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?
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?
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?
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?
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.
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?
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
--
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
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.
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?
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
--
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
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.