I saw these messages in the elasticsearch logs when the curator is failing
to attempt the deletion of an old index
org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException:
failed to process cluster event (delete-index [logstash-2014.01.02]) within
30s
at
org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:239)
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:724)
I know this is a late reply, but in case anyone else sees this:
Curator timed out its connection after waiting for 30 seconds. You can
increase the value with --timeout should something like this happen to you.
Truthfully, though, a delete operation that takes longer than even 3
seconds is indicative of an overloaded cluster.
--Aaron
On Monday, July 14, 2014 4:07:48 PM UTC-6, Nikhil Mulley wrote:
I saw these messages in the elasticsearch logs when the curator is failing
to attempt the deletion of an old index
org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException:
failed to process cluster event (delete-index [logstash-2014.01.02]) within
30s
at
org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:239)
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:724)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.