# Optimizing to compress, already at 1 segment

**URL:** https://discuss.elastic.co/t/optimizing-to-compress-already-at-1-segment/8948
**Category:** Elasticsearch
**Created:** [September 6, 2012, 10:53pm UTC](https://discuss.elastic.co/t/optimizing-to-compress-already-at-1-segment/8948 "2012-09-06T22:53:16Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Chuck\_McKenzie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chuck_mckenzie/32/19660_2.png) [@Chuck\_McKenzie](https://discuss.elastic.co/u/Chuck_McKenzie)
#### Post date: [September 6, 2012, 10:53pm UTC](https://discuss.elastic.co/t/optimizing-to-compress-already-at-1-segment/8948/1 "2012-09-06T22:53:16Z")

</div>

I've set index.store.compress.stored to true on some indices that I've done  
adding data to, but they've already been optimized down to one segment.  
How do I force a reoptimization with compression?

--

---

<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 6, 2017, 3:13am UTC](https://discuss.elastic.co/t/optimizing-to-compress-already-at-1-segment/8948/2 "2017-07-06T03:13:52Z")

</div>