# Cluster overshard issue

**URL:** <https://discuss.elastic.co/t/cluster-overshard-issue/337603>\
**Category:** Elasticsearch\
**Created:** [July 5, 2023, 4:45am UTC](https://discuss.elastic.co/t/cluster-overshard-issue/337603 "2023-07-05T04:45:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JasonREC](https://avatars.discourse-cdn.com/v4/letter/j/858c86/32.png) [@JasonREC](https://discuss.elastic.co/u/JasonREC)\
**Post date:** [July 5, 2023, 4:45am UTC](https://discuss.elastic.co/t/cluster-overshard-issue/337603/1 "2023-07-05T04:45:50Z")

</div>

Hi, I have question about how to solve the cluster overshard issue sot that things can get back to normal/

Currently, I am renting 2 node in 2 different zone.

 ![elastic_config](https://us1.discourse-cdn.com/elastic/original/3X/e/5/e5705e1795697b327af5d5cb6dab26e6b8433dfe.png)

And, I've encountered oversharding issue, show in the below picture

 ![instance_node_status](https://us1.discourse-cdn.com/elastic/original/3X/2/3/239beeb29025cd81198e36a16a459e22470d9a1e.png)

I have used Elastic service for past 3 years but never encoutered overshardding issue until I've added Elastic APM service 2 months ago to monitor my applications. Currently, I am mainly using Elastic APM log data to help me do further anaylsis.

But somehow, Elastic APM created so many index, If I understand correctly, each index is composed with at least 1 shard. I am guessing if the oversharding problems is caused by the elastic APM service.(correct me if I am wrong ) As below shows, there are so many small size index.

 ![trnasaction](https://us1.discourse-cdn.com/elastic/original/3X/6/7/67e5281bb56bdf2405e9af0cd6107188b658e6a7.png)  
 ![span](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1e2a0e65b304efa1e83663af0eeabcc174bcc2e7.png)  
 ![metrics-detail](https://us1.discourse-cdn.com/elastic/original/3X/1/5/151922adaa0f725642852f0ffc275e638ff8d9c8.png)  
 ![apm_error](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4c75ca50f119649200745365cdf1c0fab9c06338.png)

Could anyone give me a guide how can I fix this issue? I don't want to do scale up yet since I am not sure if the over sharding is simply due to I did not set up some crucial configuration or other thing else.

---

<div class="post-metadata">

**Author:** ![JasonREC](https://avatars.discourse-cdn.com/v4/letter/j/858c86/32.png) [@JasonREC](https://discuss.elastic.co/u/JasonREC)\
**Post date:** [July 5, 2023, 10:22am UTC](https://discuss.elastic.co/t/cluster-overshard-issue/337603/2 "2023-07-05T10:22:20Z")

</div>

Just an update, I have deleted all the index which only have 0 doc count showed in the my above pictures so the shard count has a huge drop, I wonder if this is fine ?

And, I also I wonder the below indices are ok to delete since they also have 0 doc but not sure where they come from.

 ![meaningless3](https://us1.discourse-cdn.com/elastic/original/3X/2/3/2374257eaaf3fceff7a72dba03122cb71488cf09.png)  
 ![meaningless2](https://us1.discourse-cdn.com/elastic/original/3X/0/8/089f0d582b09b92dbd266b89d1180c56c8f88e39.png)  
 ![meaningless](https://us1.discourse-cdn.com/elastic/original/3X/4/1/41f93ded9835b4fa71920afc2de205e73baf630a.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 2, 2023, 10:22am UTC](https://discuss.elastic.co/t/cluster-overshard-issue/337603/3 "2023-08-02T10:22:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.