# Transport client threadpool and down node

**URL:** <https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060>\
**Category:** Elasticsearch\
**Created:** [April 2, 2015, 10:25am UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060 "2015-04-02T10:25:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [April 2, 2015, 10:25am UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060/1 "2015-04-02T10:25:29Z")

</div>

Hello, elasticsearch java transport client , for index, is the thread spawn  
bounded? if not, is there a way to set it to a fix value? When one of a  
node in cluster is down, java transport client will remove this downed node  
from its list, right? But when the downed node has joined back into the  
cluster, does the transport client automatically add the new node back to  
its list?

Thanks.

Jason

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [April 2, 2015, 11:25am UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060/2 "2015-04-02T11:25:55Z")

</div>

You can set "client.transport.sniff" to true, then nodes are detected  
automatically

> **[Client | Java Transport Client (deprecated) \[7.17\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/client.html#transport-client)**

Jörg

On Thu, Apr 2, 2015 at 12:25 PM, Jason Wee [peichieh@gmail.com](mailto:peichieh@gmail.com) wrote:

> Hello, elasticsearch java transport client , for index, is the thread  
> spawn bounded? if not, is there a way to set it to a fix value? When one of  
> a node in cluster is down, java transport client will remove this downed  
> node from its list, right? But when the downed node has joined back into  
> the cluster, does the transport client automatically add the new node back  
> to its list?
> 
> Thanks.
> 
> Jason
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [April 2, 2015, 11:46am UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060/3 "2015-04-02T11:46:33Z")

</div>

yes, I have added all known nodes in the cluster into the transport  
client side.. so does this sniff parameter added will also work when  
the downed node come back online?

jason

On Thu, Apr 2, 2015 at 7:25 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com)  
[joergprante@gmail.com](mailto:joergprante@gmail.com) wrote:

> You can set "client.transport.sniff" to true, then nodes are detected  
> automatically
> 
> [Client | Java Transport Client (deprecated) [7.17] | Elastic](http://www.elastic.co/guide/en/elasticsearch/client/java-api/current/client.html#transport-client)
> 
> Jörg
> 
> On Thu, Apr 2, 2015 at 12:25 PM, Jason Wee [peichieh@gmail.com](mailto:peichieh@gmail.com) wrote:
> 
> > Hello, elasticsearch java transport client , for index, is the thread  
> > spawn bounded? if not, is there a way to set it to a fix value? When one of  
> > a node in cluster is down, java transport client will remove this downed  
> > node from its list, right? But when the downed node has joined back into the  
> > cluster, does the transport client automatically add the new node back to  
> > its list?
> > 
> > Thanks.
> > 
> > Jason
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com).  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com).
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [April 2, 2015, 2:13pm UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060/4 "2015-04-02T14:13:14Z")

</div>

Yes, that is the purpose of "sniff". You do not need to add all known nodes  
to the TransportClient, it will autodiscover other nodes when "sniff" is  
enabled.

Jörg

On Thu, Apr 2, 2015 at 1:46 PM, Jason Wee [peichieh@gmail.com](mailto:peichieh@gmail.com) wrote:

> yes, I have added all known nodes in the cluster into the transport  
> client side.. so does this sniff parameter added will also work when  
> the downed node come back online?
> 
> jason
> 
> On Thu, Apr 2, 2015 at 7:25 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com)  
> [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote:
> 
> > You can set "client.transport.sniff" to true, then nodes are detected  
> > automatically
> 
> [Client | Java Transport Client (deprecated) [7.17] | Elastic](http://www.elastic.co/guide/en/elasticsearch/client/java-api/current/client.html#transport-client)
> 
> > Jörg
> > 
> > On Thu, Apr 2, 2015 at 12:25 PM, Jason Wee [peichieh@gmail.com](mailto:peichieh@gmail.com) wrote:
> > 
> > > Hello, elasticsearch java transport client , for index, is the thread  
> > > spawn bounded? if not, is there a way to set it to a fix value? When  
> > > one of  
> > > a node in cluster is down, java transport client will remove this downed  
> > > node from its list, right? But when the downed node has joined back  
> > > into the  
> > > cluster, does the transport client automatically add the new node back  
> > > to  
> > > its list?
> > > 
> > > Thanks.
> > > 
> > > Jason
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an  
> > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > To view this discussion on the web visit
> 
> [https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com)  
> .
> 
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit
> 
> [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com)  
> .
> 
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEmmy2MXQ5HDUCMZqRR-hc8\_StUT3Dw5p3RGfcEEMhZdg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEmmy2MXQ5HDUCMZqRR-hc8_StUT3Dw5p3RGfcEEMhZdg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Jason\_Wee](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jason\_Wee](https://discuss.elastic.co/u/Jason_Wee)\
**Post date:** [April 10, 2015, 4:47am UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060/5 "2015-04-10T04:47:04Z")

</div>

alrighty, thanks Jörg

On Thu, Apr 2, 2015 at 10:13 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com)  
[joergprante@gmail.com](mailto:joergprante@gmail.com) wrote:

> Yes, that is the purpose of "sniff". You do not need to add all known nodes  
> to the TransportClient, it will autodiscover other nodes when "sniff" is  
> enabled.
> 
> Jörg
> 
> On Thu, Apr 2, 2015 at 1:46 PM, Jason Wee [peichieh@gmail.com](mailto:peichieh@gmail.com) wrote:
> 
> > yes, I have added all known nodes in the cluster into the transport  
> > client side.. so does this sniff parameter added will also work when  
> > the downed node come back online?
> > 
> > jason
> > 
> > On Thu, Apr 2, 2015 at 7:25 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com)  
> > [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote:
> > 
> > > You can set "client.transport.sniff" to true, then nodes are detected  
> > > automatically
> > > 
> > > [Client | Java Transport Client (deprecated) [7.17] | Elastic](http://www.elastic.co/guide/en/elasticsearch/client/java-api/current/client.html#transport-client)
> > > 
> > > Jörg
> > > 
> > > On Thu, Apr 2, 2015 at 12:25 PM, Jason Wee [peichieh@gmail.com](mailto:peichieh@gmail.com) wrote:
> > > 
> > > > Hello, elasticsearch java transport client , for index, is the thread  
> > > > spawn bounded? if not, is there a way to set it to a fix value? When  
> > > > one of  
> > > > a node in cluster is down, java transport client will remove this  
> > > > downed  
> > > > node from its list, right? But when the downed node has joined back  
> > > > into the  
> > > > cluster, does the transport client automatically add the new node back  
> > > > to  
> > > > its list?
> > > > 
> > > > Thanks.
> > > > 
> > > > Jason
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to the Google  
> > > > Groups  
> > > > "elasticsearch" group.  
> > > > To unsubscribe from this group and stop receiving emails from it, send  
> > > > an  
> > > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > > To view this discussion on the web visit
> > > > 
> > > > [https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com).  
> > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an  
> > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > To view this discussion on the web visit
> > > 
> > > [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com).
> > > 
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com).  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEmmy2MXQ5HDUCMZqRR-hc8\_StUT3Dw5p3RGfcEEMhZdg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEmmy2MXQ5HDUCMZqRR-hc8_StUT3Dw5p3RGfcEEMhZdg%40mail.gmail.com).
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHO4itwSZ\_zMajNUr6hwozafNbNGAb-oR0oeb6EZB7eEvZbpPw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHO4itwSZ_zMajNUr6hwozafNbNGAb-oR0oeb6EZB7eEvZbpPw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 12:20am UTC](https://discuss.elastic.co/t/transport-client-threadpool-and-down-node/23060/6 "2017-07-06T00:20:30Z")

</div>


