Hi
I testing Elastcisearch in very simple setup:
2 nodes: 1 master, 1 slave (placed on different physical servers)
1 index with no sharding
Project (PHP code) access to elastcisearch cluster via haproxy.
Immediately after initialization node, when node starts to process requests,
there are short period (about 10 seconds), when node process queries very
slow: >1s
normal query time in my tests: <100ms
In this period there are CPU usage peak (java uses up to 600% vs 30% in
normal work)
In this period there are no disk overload (Disk subsystem on server is
enough fast, RAID1: 2 x ssd)
After this period, node process queries fast (<100ms).
In case of using fixed thread pools - behavior has not changed.
State of queries in this period (search2 - slave):
host ip bulk.active bulk.queue bulk.rejected index.active
index.queue index.rejected search.active search.queue search.rejected
search1 172.16.76.21 0 0 0 0
0 0 0 0 0
search2 172.16.76.22 0 0 0 0
0 0 48 75 0
Slow queries:
[2014-07-10 12:59:18,456][TRACE][index.search.slowlog.fetch] [Kafka]
[v_v2][0] took[1s], took_millis[1014], types[default-type], stats[],
search_type[QUERY_AND_FETCH], total_shards[1] ...
[2014-07-10 12:59:18,784][TRACE][index.search.slowlog.fetch] [Kafka]
[v_v2][0] took[1.3s], took_millis[1313], types[default-type], stats[],
search_type[QUERY_AND_FETCH], total_shards[1] ...
My questions:
- Is this well-known behavior of elasticsearch?
- If not - what settings can affect and eliminate this behavior?
Thanks in advance!
P.S.: cluster config in attachment.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/199c6774-87eb-4eca-acc4-6229fc613949%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.