# Troubleshooting "search load balancer" node connectivity problems **URL:** \ **Category:** Elasticsearch\ **Created:** [January 14, 2014, 10:08am UTC](https://discuss.elastic.co/t/troubleshooting-search-load-balancer-node-connectivity-problems/15231 "2014-01-14T10:08:17Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jelle\_Smet](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@Jelle\_Smet](https://discuss.elastic.co/u/Jelle_Smet)\ **Post date:** [January 14, 2014, 10:08am UTC](https://discuss.elastic.co/t/troubleshooting-search-load-balancer-node-connectivity-problems/15231/1 "2014-01-14T10:08:17Z")
Hi list, I have 2 VM "search load balancer" nodes and 4 physical master + data nodes. The 2 search load balancer nodes get disconnected from the physical nodes very often. In the process of troubleshooting this I was wondering about following log entry: [2014-01-14 09:27:41,528][DEBUG][cluster.service] [xxx-xxx-logs-101] set local cluster state to version 512 When is this log generated? Is this automatically scheduled or does this ONLY occur when the cluster topology changes (something of which I presume shouldn't happen if all runs stable) Thanks, Jelle -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c337d016-5036-48e9-bb60-afdd7c1f0210%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c337d016-5036-48e9-bb60-afdd7c1f0210%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jelle\_Smet](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@Jelle\_Smet](https://discuss.elastic.co/u/Jelle_Smet)\ **Post date:** [February 12, 2014, 3:34pm UTC](https://discuss.elastic.co/t/troubleshooting-search-load-balancer-node-connectivity-problems/15231/2 "2014-02-12T15:34:23Z")
Never mind, Root cause was a network issue which got identified. Setting keepalive in ES kernel params solved the problem. Cheers, -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/3b4d047b-a350-477a-adb7-7aa8a8b3b610%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3b4d047b-a350-477a-adb7-7aa8a8b3b610%40googlegroups.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, 1:50am UTC](https://discuss.elastic.co/t/troubleshooting-search-load-balancer-node-connectivity-problems/15231/3 "2017-07-06T01:50:44Z")