ES Version: 1.3.5
OS: Ubuntu 14.04.1 LTS
Machine: 2 Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz, 8 GB RAM at AWS
master (ip-10-0-1-18), 2 data nodes (ip-10-0-1-19, ip-10-0-1-20)
*After upgrading from ES 1.1.2...*
1. Startup ES on master
2. All nodes join cluster
3. [2014-12-03 20:30:54,789][INFO ][gateway ]
[ip-10-0-1-18.ec2.internal] recovered [157] indices into cluster_state
4. Checked health a few times
curl -XGET localhost:9200/_cat/health?v
5. 6 minutes after cluster recovery initiates (and 5:20 after the recovery
finishes), the log on the master node (10.0.1.18) reports:
[2014-12-03 20:36:57,532][DEBUG][action.admin.cluster.node.stats]
[ip-10-0-1-18.ec2.internal] failed to execute on node
[pYi3z5PgRh6msJX_armz_A]
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[ip-10-0-1-20.ec2.internal][inet[/10.0.1.20:9300]][cluster/nodes/stats/n]
request_id [17564] timed out after [15001ms]
at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:356)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
6. Every 30 seconds or 60 seconds, the above error is reported for one or
more of the data nodes
7. During this time, queries (search, index, etc.) don’t return. They hang
until the error state temporarily resolves itself (a varying time around
15-20 minutes) at which point the expected result is returned.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/edebdf27-a766-4ba0-814d-6946d9181f68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
