Why Does the Disk Usage Increase After the delete_by_query Command Was Executed to Delete Data?
Running the delete_by_query command can only add a deletion mark to the target data instead of really deleting it. When you search for data, all data is searched and the data with the deletion mark is filtered out.
The space occupied by an index with the deletion mark will not be released immediately after you call the disk deletion API. The disk space is released only when the segment merge is performed next time.
Querying the data with deletion mark occupies disk space. In this case, the disk usage increases when you run the disk deletion commands.
Open Source Search Engine Consulting FAQs
- How Do I Set the Numbers of Index Copies to 0 in Batches?
- Why All New Index Shards Are Allocated to the Same Node?
- How Do I Create a Type Under an Index in an Elasticsearch 7.x Cluster?
- How Do I Configure a Two-Replica CSS Cluster?
- Can I Change the Number of Shards to Four with Two Replicas When There Is One Shard Set in the JSON File?
- What Are the Impacts If an Elasticsearch Cluster Has Too Many Shards?
- How Do I Check the Numbers of Shards and Replicas in a Cluster on the CSS Console?
- How Do I Query Index Data on Kibana in an ES Cluster?
- Can I Stop a CSS Cluster?
- Does the Value i of node.roles Indicate an Ingest Node?
- How Do I Set the Default Maximum Number of Records Displayed on a Page for an Elasticsearch Cluster
- How Do I Update the Lifecycle Policy of an Elasticsearch Cluster?
- How Do I Configure the Threshold for CSS Slow Query Logs?
- How Do I Delete Index Data?
- How Do I Clear the Cache of a CSS Cluster?
- Why Does the Disk Usage Increase After the delete_by_query Command Was Executed to Delete Data?
- How Do I Clear Expired Data to Release Storage Space?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore