# Ability to blacklist nodes on the fly

**URL:** <https://discuss.elastic.co/t/ability-to-blacklist-nodes-on-the-fly/38930>\
**Category:** Elasticsearch\
**Created:** [January 12, 2016, 3:15am UTC](https://discuss.elastic.co/t/ability-to-blacklist-nodes-on-the-fly/38930 "2016-01-12T03:15:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nirajpatel](https://avatars.discourse-cdn.com/v4/letter/n/7993a0/32.png) [@nirajpatel](https://discuss.elastic.co/u/nirajpatel)\
**Post date:** [January 12, 2016, 3:15am UTC](https://discuss.elastic.co/t/ability-to-blacklist-nodes-on-the-fly/38930/1 "2016-01-12T03:15:38Z")

</div>

Hi! I was wondering if there was any ability to blacklist a node while, say, it is recovering. Trying to route GETs, indexing and search to a recovering index can cause the node to fall out of the cluster or can cause the cluster to pause altogether. Is there a way to blacklist a node using the TransportClient that way no traffic is routed to a particular node (or anything similar)? Thanks!

---

<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:** [July 5, 2017, 11:25pm UTC](https://discuss.elastic.co/t/ability-to-blacklist-nodes-on-the-fly/38930/2 "2017-07-05T23:25:19Z")

</div>