# ES cluster becomes unresponsive **URL:** \ **Category:** Elasticsearch\ **Created:** [May 28, 2013, 8:19am UTC](https://discuss.elastic.co/t/es-cluster-becomes-unresponsive/12141 "2013-05-28T08:19:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Lee\_Briggs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lee_briggs/32/2090_2.png) [@Lee\_Briggs](https://discuss.elastic.co/u/Lee_Briggs)\ **Post date:** [May 28, 2013, 8:19am UTC](https://discuss.elastic.co/t/es-cluster-becomes-unresponsive/12141/1 "2013-05-28T08:19:19Z")
I'm having a really weird issue with a logging cluster still in its infancy, and I've no idea how to tackle the problem. Essentially, after a seemingly arbitray period of time, the cluster will become unresponsive until the master node is restarted. I'm not indexing a massive amount of logs at the moment, so I don't think the volume is the problem, but mainly I can't figure out how to determine what the problem is. I've looked in the logs in all nodes on the cluster (only 3 at present) and done a query to see the cluster state, and it's fine: { "cluster\_name" : "graylog2", "status" : "green", "timed\_out" : false, "number\_of\_nodes" : 4, "number\_of\_data\_nodes" : 3, "active\_primary\_shards" : 6, "active\_shards" : 12, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 0 } However my graylog2 web interface says it cannot connect to the cluster, and using elasticsearch head I get no node information except that the status is "green" As I said, there's no error in the ES logs, but then I don't have any debug logging turned on. How can I go about troubleshooting this? I don't think the problem is related to graylog2, as I was previously trialing logstash + kibana and the problem was the same there, which I thought was a limitation of the software. Any help appreciated -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [May 30, 2013, 7:17am UTC](https://discuss.elastic.co/t/es-cluster-becomes-unresponsive/12141/2 "2013-05-30T07:17:39Z")
Hey, not sure about graylog, but doesnt it use the java transport client to connect to elasticsearch? Maybe there is a version mismatch between your elasticsearch node and the client. --Alex On Tue, May 28, 2013 at 10:19 AM, Frap [lee@brig.gs](mailto:lee@brig.gs) wrote: > I'm having a really weird issue with a logging cluster still in its > infancy, and I've no idea how to tackle the problem. > > Essentially, after a seemingly arbitray period of time, the cluster will > become unresponsive until the master node is restarted. I'm not indexing a > massive amount of logs at the moment, so I don't think the volume is the > problem, but mainly I can't figure out how to determine what the problem is. > > I've looked in the logs in all nodes on the cluster (only 3 at present) > and done a query to see the cluster state, and it's fine: > > { > "cluster\_name" : "graylog2", > "status" : "green", > "timed\_out" : false, > "number\_of\_nodes" : 4, > "number\_of\_data\_nodes" : 3, > "active\_primary\_shards" : 6, > "active\_shards" : 12, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 0 > } > > However my graylog2 web interface says it cannot connect to the cluster, > and using elasticsearch head I get no node information except that the > status is "green" > > As I said, there's no error in the ES logs, but then I don't have any > debug logging turned on. How can I go about troubleshooting this? I don't > think the problem is related to graylog2, as I was previously trialing > logstash + kibana and the problem was the same there, which I thought was a > limitation of the software. > > Any help appreciated > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:33am UTC](https://discuss.elastic.co/t/es-cluster-becomes-unresponsive/12141/3 "2017-07-06T02:33:57Z")