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

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(
at java.util.ArrayList.forEach(
at org.elasticsearch.cluster.service.MasterService$Batcher.lambda$onTimeout$1(
at org.elasticsearch.common.util.concurrent.ThreadContext$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

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.

1 Like

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