# Failed to delete index using curator
**URL:** https://discuss.elastic.co/t/failed-to-delete-index-using-curator/18664
**Category:** Elasticsearch
**Created:** [July 14, 2014, 10:07pm UTC](https://discuss.elastic.co/t/failed-to-delete-index-using-curator/18664 "2014-07-14T22:07:48Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Nikhil\_Mulley](https://discuss.elastic.co/u/Nikhil_Mulley)
#### Post date: [July 14, 2014, 10:07pm UTC](https://discuss.elastic.co/t/failed-to-delete-index-using-curator/18664/1 "2014-07-14T22:07:48Z")
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)
Any ideas?
Nikhil
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/99c5f317-fa0a-4ebe-8a9c-1bc335cd24f2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/99c5f317-fa0a-4ebe-8a9c-1bc335cd24f2%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [December 17, 2014, 9:32pm UTC](https://discuss.elastic.co/t/failed-to-delete-index-using-curator/18664/2 "2014-12-17T21:32:39Z")
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)
>
> Any ideas?
>
> Nikhil
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f78520ba-08bd-42bc-8354-7e61e308fcb9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f78520ba-08bd-42bc-8354-7e61e308fcb9%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:43am UTC](https://discuss.elastic.co/t/failed-to-delete-index-using-curator/18664/3 "2017-07-06T00:43:05Z")