Help Center> Cloud Search Service> User Guide (Paris and Amsterdam Regions)> FAQs> Resource Usage and Change> What Are the Impacts If an Elasticsearch Cluster Has Too Many Shards?

Updated on 2023-06-20 GMT+08:00

View PDF

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: Resource Usage and Change

Previous topic: Can I Change the Number of Shards to Four with Two Replicas When There Is One Shard Set in the JSON File?

Next topic: How Do I Set the Default Maximum Number of Records Displayed on a Page for an Elasticsearch Cluster

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.