# WARN messages in log followed by Exception **URL:** \ **Category:** Elasticsearch\ **Created:** [July 21, 2010, 12:31pm UTC](https://discuss.elastic.co/t/warn-messages-in-log-followed-by-exception/3132 "2010-07-21T12:31:07Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\ **Post date:** [July 21, 2010, 12:31pm UTC](https://discuss.elastic.co/t/warn-messages-in-log-followed-by-exception/3132/1 "2010-07-21T12:31:07Z")
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 ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 21, 2010, 12:35pm UTC](https://discuss.elastic.co/t/warn-messages-in-log-followed-by-exception/3132/2 "2010-07-21T12:35:50Z")
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](mailto: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 ---
**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, 4:21am UTC](https://discuss.elastic.co/t/warn-messages-in-log-followed-by-exception/3132/3 "2017-07-06T04:21:56Z")
Closed on July 6, 2017, 4:21am UTC