# Merge cannot catch up with updates

**URL:** <https://discuss.elastic.co/t/merge-cannot-catch-up-with-updates/88621>\
**Category:** Elasticsearch\
**Created:** [June 7, 2017, 7:41pm UTC](https://discuss.elastic.co/t/merge-cannot-catch-up-with-updates/88621 "2017-06-07T19:41:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![suanmeiguo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suanmeiguo/32/11758_2.png) [@suanmeiguo](https://discuss.elastic.co/u/suanmeiguo)\
**Post date:** [June 7, 2017, 7:41pm UTC](https://discuss.elastic.co/t/merge-cannot-catch-up-with-updates/88621/1 "2017-06-07T19:41:05Z")

</div>

I have a very busy cluster and using defined \_id instead of auto. So there are a lot of updates on existing documents. I see from `_stats` endpoint that the ratio between deleted document and total document is at 70% and still growing over days. I'm guessing the merge operations cannot catch up with the updates speed.

I've increased the setting `index.merge.scheduler.max_thread_count` but don't see noticeable improvement. I think that's the max but not how many current runs.

Is there any other configuration I can do to have the merge happens more frequent or faster?

Appreciate your help!

---

<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:** [July 5, 2017, 7:41pm UTC](https://discuss.elastic.co/t/merge-cannot-catch-up-with-updates/88621/2 "2017-07-05T19:41:12Z")

</div>

Closed on July 5, 2017, 7:41pm UTC

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