# No longer configurable for merge policy segments\_per\_tier?

**URL:** https://discuss.elastic.co/t/no-longer-configurable-for-merge-policy-segments-per-tier/100514
**Category:** Elasticsearch
**Created:** [September 14, 2017, 10:43am UTC](https://discuss.elastic.co/t/no-longer-configurable-for-merge-policy-segments-per-tier/100514 "2017-09-14T10:43:29Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![itplayer](https://avatars.discourse-cdn.com/v4/letter/i/d26b3c/32.png) [@itplayer](https://discuss.elastic.co/u/itplayer)
#### Post date: [September 14, 2017, 10:43am UTC](https://discuss.elastic.co/t/no-longer-configurable-for-merge-policy-segments-per-tier/100514/1 "2017-09-14T10:43:29Z")

</div>

For some reason, I tuned merge policy params ann got good performance in my project based on ES 1.7.2  
But recently I upgraded to 5.4 and it seems to me those merge policy params are not supported? Is this true and what is alternatives if I really need to use my params for merge policy?

Please help on this.  
Many thanks

---

<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: [October 12, 2017, 10:43am UTC](https://discuss.elastic.co/t/no-longer-configurable-for-merge-policy-segments-per-tier/100514/2 "2017-10-12T10:43:30Z")

</div>

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