# Exclude client node from discovery?

**URL:** <https://discuss.elastic.co/t/exclude-client-node-from-discovery/26452>\
**Category:** Elasticsearch\
**Created:** [July 29, 2015, 2:03am UTC](https://discuss.elastic.co/t/exclude-client-node-from-discovery/26452 "2015-07-29T02:03:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frkris](https://avatars.discourse-cdn.com/v4/letter/f/71c47a/32.png) [@frkris](https://discuss.elastic.co/u/frkris)\
**Post date:** [July 29, 2015, 2:03am UTC](https://discuss.elastic.co/t/exclude-client-node-from-discovery/26452/1 "2015-07-29T02:03:46Z")

</div>

We are trying to use a dedicated client node for admin-related tasks such as large batch imports, so as to not disturb the public-facing dedicated client nodes when we do a heavy import.

My issue is that since this node is essentially just a client node like any other client node, the Ruby API layer will discover it and start serving requests to it.

Any advice on how to deal with this?

---

<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:58pm UTC](https://discuss.elastic.co/t/exclude-client-node-from-discovery/26452/2 "2017-07-05T23:58:29Z")

</div>

Closed on July 5, 2017, 11:58pm UTC