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 issues on this scale.
Thanks,
Emir
On 28.10.2015 17:27, Andrii Berezhynskyi 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
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/
