Hmmm, do the segments go away when you reload the slave? Or do they hang around over even Solr restarts? If they're temporary then you may be seeing them held by one searcher while another one warms up.
Best, Erick On Wed, Oct 28, 2015 at 9:27 AM, Andrii Berezhynskyi <andrii.berezhyns...@home24.de> wrote: > Hi all! > > We have master-slave configuration. Slaves are replicated on optimize. > Sometimes (not always) it happens that slave has two segments after > replication. I always thought that optimize is all about having only one > segment in your read replica. During this time when slave has two segments > we are experiencing higher response time and higher CPU usage. Is it > somehow possible to prevent slave from having two segments in > slave-replicated-on-optimize configuration? > > Segments info shows the following for these two segments: > > Segment *_1kxw*: > #docs: > 167 841 > #dels: > 161 > size: > 96 985 075 bytes > age: > 2015-10-28T16:10:01.894Z > source: > merge > > Segment *_1kxv*: > #docs: > 160 > #dels: > 0 > size: > 270 075 bytes > age: > 2015-10-28T16:10:07.897Z > source: > flush > > Best regards, > Andrii
