# Recommended way to delete an index **URL:** \ **Category:** Elasticsearch\ **Created:** [June 25, 2017, 8:38pm UTC](https://discuss.elastic.co/t/recommended-way-to-delete-an-index/90769 "2017-06-25T20:38:21Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![animageofmine](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@animageofmine](https://discuss.elastic.co/u/animageofmine)\ **Post date:** [July 18, 2017, 12:37am UTC](https://discuss.elastic.co/t/recommended-way-to-delete-an-index/90769/14 "2017-07-18T00:37:34Z")
ok :-). Default is way to high for most of the cases for our system. If you get a chance to look at this question, I would really appreciate that. > [@Does transport client cache nodes in the cluster?](https://discuss.elastic.co/t/does-transport-client-cache-nodes-in-the-cluster/93243): > > We use transport client (elastic4s) to communicate with ES cluster via consul. One of the problems we have seen so far is that the client keeps sending queries to the dead nodes. For example, if the data node node1 is dockerized and if you stop the process inside the container (for testing purpose), but the container is still on, consul does not redirect the queries to that node. However, we still see the queries routed to the dead node node1. I know the client is cluster aware, but I am not s… --- _[View the full topic](https://discuss.elastic.co/t/recommended-way-to-delete-an-index/90769)._