Help Center>
Cloud Search Service>
FAQs>
Open Source Search Engine Consulting>
What Are the Impacts If an Elasticsearch Cluster Has Too Many Shards?
Updated on 2023-09-20 GMT+08:00
What Are the Impacts If an Elasticsearch Cluster Has Too Many Shards?
- A large number of shards in a cluster slows down shard creation.
- If automatic index creation is enabled, slow index creation may cause a large number of write requests to be stacked in the memory or result in a cluster break down.
- If there are too many shards and you cannot properly monitor workloads, the number of records in a single shard may exceed the threshold, and write requests may be denied.
Parent topic: Open Source Search Engine Consulting
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore