# Disable compound file storage format

**URL:** <https://discuss.elastic.co/t/disable-compound-file-storage-format/13799>\
**Category:** Elasticsearch\
**Created:** [September 30, 2013, 7:28am UTC](https://discuss.elastic.co/t/disable-compound-file-storage-format/13799 "2013-09-30T07:28:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hanish\_Bansal](https://avatars.discourse-cdn.com/v4/letter/h/e36b37/32.png) [@Hanish\_Bansal](https://discuss.elastic.co/u/Hanish_Bansal)\
**Post date:** [September 30, 2013, 7:28am UTC](https://discuss.elastic.co/t/disable-compound-file-storage-format/13799/1 "2013-09-30T07:28:03Z")

</div>

Hi All,

I am upgrading my elastic-search from elasticsearch-0.90.0.RC2 to  
elasticsearch-0.90.5.

As default file compound format is false so files should be stored as  
normal files like .fdx,.fdt and many other formats. This is expected  
behaviour which i was getting in elasticsearch-0.90.0.RC2.

But elasticsearch-0.90.5 storing the data as compound format.  
I tried to disable compound file storage by defining "_index.compound\_format:  
false_" in config file but it is giving the same behaviour.  
When i set "_index.refresh\_interval: 1_" in config file then it started  
storing the data as normal. After restarting elastic-search it again  
convert the data as compound format.

Any suggestion how to disable compound file storage format ?

--  
_Thanks & Regards_  
_Hanish Bansal_

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\
**Post date:** [September 30, 2013, 2:27pm UTC](https://discuss.elastic.co/t/disable-compound-file-storage-format/13799/2 "2013-09-30T14:27:15Z")

</div>

Newly flushed segments are will be written into the compound format regards  
less of the `compound_format` setting. This setting applies on when  
segments get merged into bigger segments. In general means that only small  
segments will have the compound file format.

What is the reason why you don't want compound segments? The idea behind  
compound file format is to reduce the number of open file descriptors to a  
Lucene index (shard). Since segments get flushed all the time due to  
frequent refresh (1 second by default), there can be some compound segments.

On 30 September 2013 09:28, Hanish Bansal  
[hanish.bansal.agarwal@gmail.com](mailto:hanish.bansal.agarwal@gmail.com)wrote:

> Hi All,
> 
> I am upgrading my elastic-search from elasticsearch-0.90.0.RC2 to  
> elasticsearch-0.90.5.
> 
> As default file compound format is false so files should be stored as  
> normal files like .fdx,.fdt and many other formats. This is expected  
> behaviour which i was getting in elasticsearch-0.90.0.RC2.
> 
> But elasticsearch-0.90.5 storing the data as compound format.  
> I tried to disable compound file storage by defining "_index.compound\_format:  
> false_" in config file but it is giving the same behaviour.  
> When i set "_index.refresh\_interval: 1_" in config file then it started  
> storing the data as normal. After restarting elastic-search it again  
> convert the data as compound format.
> 
> Any suggestion how to disable compound file storage format ?
> 
> --  
> _Thanks & Regards_  
> _Hanish Bansal_
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
Met vriendelijke groet,

Martijn van Groningen

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Igor\_Masternoy](https://avatars.discourse-cdn.com/v4/letter/i/d2c977/32.png) [@Igor\_Masternoy](https://discuss.elastic.co/u/Igor_Masternoy)\
**Post date:** [September 14, 2016, 9:21am UTC](https://discuss.elastic.co/t/disable-compound-file-storage-format/13799/3 "2016-09-14T09:21:19Z")

</div>

> [@Hanish\_Bansal](#):
>
> index.compound\_format

I think you can use these two properties:  
index:  
compound\_format: false  
compound\_on\_flush: false

As the result you will get 6 files for newly created segments. Without these properties it would be 2 files: segname.scf and segname.si.

P.S. 2 years have been passed 😉

---

<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, 10:20pm UTC](https://discuss.elastic.co/t/disable-compound-file-storage-format/13799/4 "2017-07-05T22:20:22Z")

</div>


