# Cluster takes too long to apply cluster state

**URL:** https://discuss.elastic.co/t/cluster-takes-too-long-to-apply-cluster-state/328407
**Category:** Elasticsearch
**Created:** [March 24, 2023, 1:49am UTC](https://discuss.elastic.co/t/cluster-takes-too-long-to-apply-cluster-state/328407 "2023-03-24T01:49:01Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [March 24, 2023, 6:34pm UTC](https://discuss.elastic.co/t/cluster-takes-too-long-to-apply-cluster-state/328407/4 "2023-03-24T18:34:57Z")

</div>

> [@Vadym](#):
>
> We can tolerate delete operation to be long and put some queries in queue but want to avoid nodes being kicked out of the cluster.

Hmm this sounds like a possible bug, we shouldn't be blocking cluster state updates on deletes no matter how large the indices are. Could you follow the [troubleshooting guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-fault-detection.html#cluster-fault-detection-troubleshooting) to work out what extra information to collect to dig deeper?

---

_[View the full topic](https://discuss.elastic.co/t/cluster-takes-too-long-to-apply-cluster-state/328407)._