# Is process cluster event timeout value configurable and how if yes?

**URL:** https://discuss.elastic.co/t/is-process-cluster-event-timeout-value-configurable-and-how-if-yes/219710
**Category:** Elasticsearch
**Created:** [February 18, 2020, 6:05am UTC](https://discuss.elastic.co/t/is-process-cluster-event-timeout-value-configurable-and-how-if-yes/219710 "2020-02-18T06:05:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![f02061232](https://avatars.discourse-cdn.com/v4/letter/f/bbce88/32.png) [@f02061232](https://discuss.elastic.co/u/f02061232)
#### Post date: [February 18, 2020, 6:05am UTC](https://discuss.elastic.co/t/is-process-cluster-event-timeout-value-configurable-and-how-if-yes/219710/1 "2020-02-18T06:05:22Z")

</div>

I got ProcessClusterEventTimeoutException when create/delete index, default value is 30s. Is this configurable and how to config it?

org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: failed to process cluster event (delete-index [[xxx-indexname]]) within 30s  
at org.elasticsearch.cluster.service.MasterService$Batcher.lambda$onTimeout$0(MasterService.java:124)  
at java.util.ArrayList.forEach(ArrayList.java:1249)  
at org.elasticsearch.cluster.service.MasterService$Batcher.lambda$onTimeout$1(MasterService.java:123)  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:626)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)  
at java.lang.Thread.run(Thread.java:748)

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [February 18, 2020, 10:12am UTC](https://discuss.elastic.co/t/is-process-cluster-event-timeout-value-configurable-and-how-if-yes/219710/2 "2020-02-18T10:12:05Z")

</div>

Yes, you can pass a different timeout on a request-by-request basis: `DELETE /my-index?timeout=60s&master_timeout=60s`. However, if it's exceeding the default 30-second timeout then I suspect there's something wrong with your cluster, particularly since deleting an index is an `URGENT`-priority task which should be happening well within 30 seconds.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 17, 2020, 10:15am UTC](https://discuss.elastic.co/t/is-process-cluster-event-timeout-value-configurable-and-how-if-yes/219710/3 "2020-03-17T10:15:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
