That distribution of segment sizes seems odd. Why so many medium-large segments?
Are there custom settings for merge policy? I think the default policy would avoid so many segments that are mostly deleted documents. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Oct 27, 2016, at 9:40 AM, Shawn Heisey <apa...@elyograg.org> wrote: > > On 10/27/2016 9:50 AM, Yonik Seeley wrote: >> On Thu, Oct 27, 2016 at 9:56 AM, Arkadi Colson <ark...@smartbit.be> >> wrote: >>> Thanks for the answer! Do you know if there is a way to trigger an >>> optimize for only 1 shard and not the whole collection at once? >> Adding a "distrib=false" parameter should work I think. > > Last time I checked, which I admit has been a little while, optimize > ignored distrib and proceeded with a sequential optimize of every core > in the collection. > > Thanks, > Shawn >
