Erick, they are not going away after reload.
Emir, increased cpu and response time are on slaves. On all slaves. Here is
a thread dump
https://gist.github.com/andriiberezhynskyi/739d59cf78b043d653da (though not
sure that I did it right, I used jstack -F PID).
Thanks for your help!
Hi Andrii,
Observed high CPU is on master or slave? If on slave, is it on all
slaves? Can you do thread dump and see if what is running.
Based on numbers this seems like small index and one segment is flush
with only 160 doc. Anyway, this is small and something is really wrong
if you notice i
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
wrote:
> Hi all!
>
> We have
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
