# Clarify on transport client over coordinating nodes with sniffing enabled

**URL:** <https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440>\
**Category:** Elasticsearch\
**Created:** [October 10, 2017, 9:33pm UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440 "2017-10-10T21:33:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hexin\_Wang](https://avatars.discourse-cdn.com/v4/letter/h/c0e974/32.png) [@Hexin\_Wang](https://discuss.elastic.co/u/Hexin_Wang)\
**Post date:** [October 10, 2017, 9:33pm UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440/1 "2017-10-10T21:33:57Z")

</div>

If I initialize a transport client with only coordinating nodes specified, should I disable sniffing by default so the index/search request is guaranteed to go to coordinating nodes only? Is there any performance hit for indexing since now there is one extra hop from coordinator node to data node?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 11, 2017, 7:50am UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440/2 "2017-10-11T07:50:51Z")

</div>

By default sniffing est disabled.  
Having coordinating nodes is good IMO unless you have only a few data nodes.

BTW use the REST Client instead if you are starting a new project

---

<div class="post-metadata">

**Author:** ![Hexin\_Wang](https://avatars.discourse-cdn.com/v4/letter/h/c0e974/32.png) [@Hexin\_Wang](https://discuss.elastic.co/u/Hexin_Wang)\
**Post date:** [October 11, 2017, 10:18pm UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440/3 "2017-10-11T22:18:21Z")

</div>

Thanks @dadoonet. Given that data node might still need to route the request to the right shard, can I say performance with coordinator should not deviate that much compared with directly sending request to data node?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 12, 2017, 4:45am UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440/4 "2017-10-12T04:45:28Z")

</div>

Exact

---

<div class="post-metadata">

**Author:** ![Hexin\_Wang](https://avatars.discourse-cdn.com/v4/letter/h/c0e974/32.png) [@Hexin\_Wang](https://discuss.elastic.co/u/Hexin_Wang)\
**Post date:** [October 12, 2017, 8:44am UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440/5 "2017-10-12T08:44:50Z")

</div>

Got it. 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:** [November 9, 2017, 8:44am UTC](https://discuss.elastic.co/t/clarify-on-transport-client-over-coordinating-nodes-with-sniffing-enabled/103440/6 "2017-11-09T08:44:51Z")

</div>

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