Hi Greg, I believe max_num_segments is technically a hint that can be overridden by the merge algorithm if it decides to. You might try simply re-running the optimize again to get from ~25 down closer to 1. Sorry but I don't know of any way to see when the optimize is finished - it's really just forcing a merge so looking at merge stats is what you want.
Hope that helps. Andrew On Aug 15, 2014, at 8:01 PM, Gregory Sutcliffe <gsutcli...@publishthis.com> wrote: > Hey Guys, > We were doing some updates to our es(1.3.1) clusters recently and had some > questions about _optimize. We optimized with max_num_segments 1 and we're > still seeing ~25 segments per shard. The index that was optimized had no > writes going to it during the time, it was actually freshly re-opened after > an upgrade. Also, are there any tricks to seeing when an optimize is done > other that watching merges stats and disk IO? Maybe some data in marvel? > > Thanks for your assistance, > Greg > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/17622c72-f004-4fda-92fb-dda393a64807%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/88238DE4-AFC4-41D0-B495-ED9938D7CB9C%40elasticsearch.com. For more options, visit https://groups.google.com/d/optout.
