0.19.9 failed to get local cluster state

Elastic Stack Elasticsearch
1

I have one cluster with 12 node (Server), with elasticsearch 0.19.9,
and another host with ES client.

All the time i have the msg below.

2012-08-29_18:55:28.32015 [29 Aug 2012 15:55:28,319]
[ElasticSearchSearch] [INFO] (Log4jESLogger.java:109) - [Commando]
failed to get local cluster state for
[Perseus][xF8zE3ODSGemO51Dqdciag][inet[/10.38.0.76:9300]],
disconnecting...
2012-08-29_18:55:28.32019
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[Perseus][inet[/10.38.0.76:9300]][cluster/state] request_id [809]
timed out after [5000ms]
2012-08-29_18:55:28.32019 at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:347)
2012-08-29_18:55:28.32022 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
2012-08-29_18:55:28.32022 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
2012-08-29_18:55:28.32023 at java.lang.Thread.run(Thread.java:679)

In my cluster don't exist [Commando] node (server), Anyone know why
printing this message?
My Search performance is very bad.

--
Gustavo Maia

--

2

Are you using the transport client? Are you setting sniffing to true for that transport client? In that case, in an async manner, the nodes will be sniffed out of the list of addresses you provide, and maybe some of them are not accessible? Note, the IP address used when sniffing is enabled is not the one you provide as addresses to the transport client, but the "publish_host" of each node.

On Aug 29, 2012, at 10:02 PM, Gustavo Maia gustavobbmaia@gmail.com wrote:

I have one cluster with 12 node (Server), with elasticsearch 0.19.9,
and another host with ES client.

All the time i have the msg below.

2012-08-29_18:55:28.32015 [29 Aug 2012 15:55:28,319]
[ElasticSearchSearch] [INFO] (Log4jESLogger.java:109) - [Commando]
failed to get local cluster state for
[Perseus][xF8zE3ODSGemO51Dqdciag][inet[/10.38.0.76:9300]],
disconnecting...
2012-08-29_18:55:28.32019
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[Perseus][inet[/10.38.0.76:9300]][cluster/state] request_id [809]
timed out after [5000ms]
2012-08-29_18:55:28.32019 at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:347)
2012-08-29_18:55:28.32022 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
2012-08-29_18:55:28.32022 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
2012-08-29_18:55:28.32023 at java.lang.Thread.run(Thread.java:679)

In my cluster don't exist [Commando] node (server), Anyone know why
printing this message?
My Search performance is very bad.

--
Gustavo Maia

--

--

1 Like
3

Hi there,

I am also getting the same error. We have enabled the multicast and using
the java tcp client.
Could you please tell me the way to resolve this issue?

2014-01-04 16:22:37,251 INFO [org.elasticsearch.client.transport]
(elasticsearch[Scott Washington][generic][T#12]) [Scott Washington] failed
to get local cluster state for
[es-acis-d02][ZFpe67GFQtifbJmO0RpjBA][inet[/10.10.2.107:14202]]{machine_id=godavari17,
master=false}, disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[es-acis-d02][inet[/10.10.2.107:14202]][cluster/state] request_id [1024722]
timed out after [5000ms]
at
org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:342)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

Thanks,
Muthusamy J

On Wednesday, August 29, 2012 2:21:25 PM UTC-7, kimchy wrote:

Are you using the transport client? Are you setting sniffing to true for
that transport client? In that case, in an async manner, the nodes will
be sniffed out of the list of addresses you provide, and maybe some of them
are not accessible? Note, the IP address used when sniffing is enabled is
not the one you provide as addresses to the transport client, but the
"publish_host" of each node.

On Aug 29, 2012, at 10:02 PM, Gustavo Maia <gustav...@gmail.com<javascript:>>
wrote:

I have one cluster with 12 node (Server), with elasticsearch 0.19.9,
and another host with ES client.

All the time i have the msg below.

2012-08-29_18:55:28.32015 [29 Aug 2012 15:55:28,319]
[ElasticSearchSearch] [INFO] (Log4jESLogger.java:109) - [Commando]
failed to get local cluster state for
[Perseus][xF8zE3ODSGemO51Dqdciag][inet[/10.38.0.76:9300]],
disconnecting...
2012-08-29_18:55:28.32019
org.elasticsearch.transport.ReceiveTimeoutTransportException:
[Perseus][inet[/10.38.0.76:9300]][cluster/state] request_id [809]
timed out after [5000ms]
2012-08-29_18:55:28.32019 at

org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:347)

2012-08-29_18:55:28.32022 at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

2012-08-29_18:55:28.32022 at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

2012-08-29_18:55:28.32023 at
java.lang.Thread.run(Thread.java:679)

In my cluster don't exist [Commando] node (server), Anyone know why
printing this message?
My Search performance is very bad.

--
Gustavo Maia

--

--
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/c9065481-b289-4db8-a37b-93693d5ed5c7%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.