# \_reindex task creates loads of bulk requests and destroys audit log disk space
**URL:** https://discuss.elastic.co/t/reindex-task-creates-loads-of-bulk-requests-and-destroys-audit-log-disk-space/293884
**Category:** Elasticsearch
**Tags:** reindex
**Created:** [January 10, 2022, 11:52am UTC](https://discuss.elastic.co/t/reindex-task-creates-loads-of-bulk-requests-and-destroys-audit-log-disk-space/293884 "2022-01-10T11:52:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@can.ozdemir](https://discuss.elastic.co/u/can.ozdemir)
#### Post date: [January 10, 2022, 11:52am UTC](https://discuss.elastic.co/t/reindex-task-creates-loads-of-bulk-requests-and-destroys-audit-log-disk-space/293884/1 "2022-01-10T11:52:10Z")
Hello,
I recently tried to reindex 40ish smaller indexes into on big index for better distribution. reindexing was going fine I was watching the process on monitoring ui, and the task was ok no failed shards. After quite sometime almost 6 hours, the indexing was half way done. Our unix admin sends us an email about a disk alarm, I went into the machine which indeed had the primary shard of the destination index, I was reindexing to. I tailed the last audit.json file which is now 25 GBs and found out the machine constantly logs bulk write requests into its audit logs, I cancelled the task since we did not have enough space on the machine for further logging.
Do elastic have a way of not logging a certain task under auditing can we give a parameter to cancel logging? or do i need to exclude that action from audit logs and restart each node to be able to finish this reindex without exploding my disks?
Best regards.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 7, 2022, 11:52am UTC](https://discuss.elastic.co/t/reindex-task-creates-loads-of-bulk-requests-and-destroys-audit-log-disk-space/293884/2 "2022-02-07T11:52:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.