WARN messages in log followed by Exception


(Lukáš Vlček) #1

Hi,

I have been noticing this for some time now, I am getting the following WARN
messages in server node log file (I added an extra line after each log line
for better readability):

[14:16:56,984][INFO ][cluster.service ] [Legacy] removed {[Tom
Thumb][d2393033-d032-4f46-81d2-35971643593b][inet[/127.0.0.1:9307]]{client=true,
data=false, zen.master=false},}, reason: zen-disco-node_left([Tom
Thumb][d2393033-d032-4f46-81d2-35971643593b][inet[/127.0.0.1:9307]]{client=true,
data=false, zen.master=false})

[14:16:56,988][INFO ][cluster.service ] [Legacy] removed
{[Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false},}, reason:
zen-disco-node_left([Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false})

[14:16:57,006][WARN ][discovery.zen.publish ] [Legacy] failed to send
cluster state to [[Tom
Thumb][d2393033-d032-4f46-81d2-35971643593b][inet[/127.0.0.1:9307]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...

org.elasticsearch.transport.NodeDisconnectedException: [Tom
Thumb][inet[/127.0.0.1:9307]][discovery/zen/publish]
[14:16:57,006][WARN ][discovery.zen.publish ] [Legacy] failed to send
cluster state to
[[Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...

org.elasticsearch.transport.NodeDisconnectedException:
[Redeemer][inet[/127.0.0.1:9304]][discovery/zen/publish]
[14:16:57,006][WARN ][discovery.zen.publish ] [Legacy] failed to send
cluster state to
[[Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...

org.elasticsearch.transport.NodeDisconnectedException:
[Redeemer][inet[/127.0.0.1:9304]][discovery/zen/publish]

What happens here is that I am disconnecting several clients from a server
node. In this case we can see that two clients were disconnected [Tom Thumb]
and [Redeemer] and right after that the server node failed to send a cluster
state to them (there were another 7 clients disconnected from server before
that - not sure if that is imoprtant). In the end there is some exception
from Remeeder. I am running master build.

Regards,
Lukas


(Shay Banon) #2

Thats ok, maybe the logging should not be WARN just DEBUG. The correct
course of action is taken.

-shay.banon

On Wed, Jul 21, 2010 at 3:31 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Hi,

I have been noticing this for some time now, I am getting the following
WARN messages in server node log file (I added an extra line after each log
line for better readability):

[14:16:56,984][INFO ][cluster.service ] [Legacy] removed {[Tom
Thumb][d2393033-d032-4f46-81d2-35971643593b][inet[/127.0.0.1:9307]]{client=true,
data=false, zen.master=false},}, reason: zen-disco-node_left([Tom
Thumb][d2393033-d032-4f46-81d2-35971643593b][inet[/127.0.0.1:9307]]{client=true,
data=false, zen.master=false})

[14:16:56,988][INFO ][cluster.service ] [Legacy] removed
{[Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false},}, reason:
zen-disco-node_left([Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false})

[14:16:57,006][WARN ][discovery.zen.publish ] [Legacy] failed to send
cluster state to [[Tom
Thumb][d2393033-d032-4f46-81d2-35971643593b][inet[/127.0.0.1:9307]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...

org.elasticsearch.transport.NodeDisconnectedException: [Tom
Thumb][inet[/127.0.0.1:9307]][discovery/zen/publish]
[14:16:57,006][WARN ][discovery.zen.publish ] [Legacy] failed to send
cluster state to
[[Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...

org.elasticsearch.transport.NodeDisconnectedException:
[Redeemer][inet[/127.0.0.1:9304]][discovery/zen/publish]
[14:16:57,006][WARN ][discovery.zen.publish ] [Legacy] failed to send
cluster state to
[[Redeemer][93741ad0-0750-45ab-a2d1-fe633a1552d7][inet[/127.0.0.1:9304]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...

org.elasticsearch.transport.NodeDisconnectedException:
[Redeemer][inet[/127.0.0.1:9304]][discovery/zen/publish]

What happens here is that I am disconnecting several clients from a server
node. In this case we can see that two clients were disconnected [Tom Thumb]
and [Redeemer] and right after that the server node failed to send a cluster
state to them (there were another 7 clients disconnected from server before
that - not sure if that is imoprtant). In the end there is some exception
from Remeeder. I am running master build.

Regards,
Lukas


(system) #3