# About merge policy for a segment of small size
**URL:** https://discuss.elastic.co/t/about-merge-policy-for-a-segment-of-small-size/229212
**Category:** Elasticsearch
**Created:** [April 22, 2020, 8:45am UTC](https://discuss.elastic.co/t/about-merge-policy-for-a-segment-of-small-size/229212 "2020-04-22T08:45:24Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Hyunsoo\_Shim](https://discuss.elastic.co/u/Hyunsoo_Shim)
#### Post date: [April 22, 2020, 8:45am UTC](https://discuss.elastic.co/t/about-merge-policy-for-a-segment-of-small-size/229212/1 "2020-04-22T08:45:25Z")
Hello,
I have a question about merge policy for a segment of small size.
I have found a below segment from a shard and have expected that would be merged with new one since the size seemed to be small (just 3.3mb).
> "\_ks" : {
> "generation" : 748,
> "num\_docs" : 355,
> "deleted\_docs" : 0,
> "size\_in\_bytes" : 3546268,
> "memory\_in\_bytes" : 41931,
> "committed" : true,
> "search" : true,
> "version" : "7.5.0",
> "compound" : true,
> "attributes" : {
> "Lucene50StoredFieldsFormat.mode" : "BEST\_SPEED"
> }
> }
But that segment is remained so long time although force merge is called..
If a segment size is over floor\_segment value(2MB), Would that segment not be merged to new one without other trigger point(e.g., delete\_weight)?
Or is there any policy to trigger merge with segment size?
FYI, I am using ES 6.5.2 version.
Thanks.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 20, 2020, 8:45am UTC](https://discuss.elastic.co/t/about-merge-policy-for-a-segment-of-small-size/229212/2 "2020-05-20T08:45:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.