Transport client threadpool and down node

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

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 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.
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?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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
joergprante@gmail.com wrote:

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

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 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com.
For more options, visit 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com.

For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 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
joergprante@gmail.com wrote:

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

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 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.
To view this discussion on the web visit

https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com
.

For more options, visit 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.
To view this discussion on the web visit

https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com
.

For more options, visit 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEmmy2MXQ5HDUCMZqRR-hc8_StUT3Dw5p3RGfcEEMhZdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

alrighty, thanks Jörg

On Thu, Apr 2, 2015 at 10:13 PM, joergprante@gmail.com
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 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
joergprante@gmail.com wrote:

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

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 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.
To view this discussion on the web visit

https://groups.google.com/d/msgid/elasticsearch/639ada4d-1176-4e2a-b437-a81f8ec72d4f%40googlegroups.com.
For more options, visit 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.
To view this discussion on the web visit

https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8CP09KftpumV29BnTsx%2BjJ6ttK4BzM3ZSvHv07B7wkQ%40mail.gmail.com.

For more options, visit 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAHO4itzWC4YJm7Km3vbaXcSPvPMbzXc45PzugOoY4fD3Jo9ukg%40mail.gmail.com.
For more options, visit 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEmmy2MXQ5HDUCMZqRR-hc8_StUT3Dw5p3RGfcEEMhZdg%40mail.gmail.com.

For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHO4itwSZ_zMajNUr6hwozafNbNGAb-oR0oeb6EZB7eEvZbpPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.