Not part of cluster


(dominik symonowicz) #1

Hello folks.

So i have problem i see warning...
"WARNING: [Johnny Ohm] Node [Smuggler II][4rNtWrqJSLKKkOB0uhXntg]
[inet[/10.0.5.69:9300]] not part of the cluster Cluster [dom],
ignoring...
13-Oct-2011 10:57:27
org.elasticsearch.common.logging.slf4j.Slf4jESLogger internalWarn"
which appear endlessly.... which means somebody screw up
settings ....which what can happen and it is expected ,but i want
handle that by throw exception ....
.Yes,i want... if somebody mess name of cluster ,then i want put to
logic to handle that .. (for example switch off server , send email
to Mr. Kimchy with complain that finding useful docs about
elasticsearch is like looking for needle in the hay in dark room


(Shay Banon) #2

When happens is that you use the TransportClient, and connect to a node that
does not have the same cluster name as the TransportClient. You need to make
sure to configure the transport client with the correct set of nodes. I
guess it make sense to be able to register a callback to be notified that
the listed node is not part of the cluster, or something similar, open an
issue.

On Thu, Oct 13, 2011 at 12:05 PM, dominik symonowicz dmspastor@gmail.comwrote:

Hello folks.

So i have problem i see warning...
"WARNING: [Johnny Ohm] Node [Smuggler II][4rNtWrqJSLKKkOB0uhXntg]
[inet[/10.0.5.69:9300]] not part of the cluster Cluster [dom],
ignoring...
13-Oct-2011 10:57:27
org.elasticsearch.common.logging.slf4j.Slf4jESLogger internalWarn"
which appear endlessly.... which means somebody screw up
settings ....which what can happen and it is expected ,but i want
handle that by throw exception ....
.Yes,i want... if somebody mess name of cluster ,then i want put to
logic to handle that .. (for example switch off server , send email
to Mr. Kimchy with complain that finding useful docs about
elasticsearch is like looking for needle in the hay in dark room


(Yann Barraud) #3

Hi,

Do we have an option to be notified if we are not connected to a cluster ?

Thanks.

Le vendredi 14 octobre 2011 14:09:04 UTC+2, kimchy a écrit :

When happens is that you use the TransportClient, and connect to a node
that does not have the same cluster name as the TransportClient. You need
to make sure to configure the transport client with the correct set of
nodes. I guess it make sense to be able to register a callback to be
notified that the listed node is not part of the cluster, or something
similar, open an issue.

On Thu, Oct 13, 2011 at 12:05 PM, dominik symonowicz <dmsp...@gmail.com<javascript:>

wrote:

Hello folks.

So i have problem i see warning...
"WARNING: [Johnny Ohm] Node [Smuggler II][4rNtWrqJSLKKkOB0uhXntg]
[inet[/10.0.5.69:9300]] not part of the cluster Cluster [dom],
ignoring...
13-Oct-2011 10:57:27
org.elasticsearch.common.logging.slf4j.Slf4jESLogger internalWarn"
which appear endlessly.... which means somebody screw up
settings ....which what can happen and it is expected ,but i want
handle that by throw exception ....
.Yes,i want... if somebody mess name of cluster ,then i want put to
logic to handle that .. (for example switch off server , send email
to Mr. Kimchy with complain that finding useful docs about
elasticsearch is like looking for needle in the hay in dark room

--
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/c59a34c4-f1e5-4df7-9e4e-7b5503bf16c0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #4

After client.addTransportAddress(...), you can check if
client.connectedNodes() is not null and is not empty, then TransportClient
is connected.

Jörg

--
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/CAKdsXoEHuXKJ2QTaHZgEGASw3PTOi3u2XzLDG_6AWO1j_vV-2g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Yann Barraud) #5

Hi,

I also opened an issue after talking to Shay

Cordialement,
Yann Barraud

2013/12/30 joergprante@gmail.com joergprante@gmail.com

After client.addTransportAddress(...), you can check if
client.connectedNodes() is not null and is not empty, then TransportClient
is connected.

Jörg

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/br8ZXUGni20/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEHuXKJ2QTaHZgEGASw3PTOi3u2XzLDG_6AWO1j_vV-2g%40mail.gmail.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
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/CA%2BhvuXcuXNZh4P50y8MT9xFrCv6VL9Ju3NR3bRHw1rLodqRr5g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #6