# Kibana flapping between red and green **URL:** \ **Category:** Kibana\ **Created:** [December 3, 2015, 10:50pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328 "2015-12-03T22:50:09Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\ **Post date:** [December 3, 2015, 10:50pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/1 "2015-12-03T22:50:09Z")
Hi List, Running an ES2.1 cluster with 4 nodes and Kibana 4.3. I am constantly seeing this when Kibana starts up: ``` log [09:39:20.395] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms log [09:39:24.367] [info][status][plugin:elasticsearch] Status changed from red to green - Kibana index ready log [09:39:40.273] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms log [09:39:42.808] [info][status][plugin:elasticsearch] Status changed from red to green - Kibana index ready log [09:40:15.028] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms log [09:40:17.557] [info][status][plugin:elasticsearch] Status changed from red to green - Kibana index ready log [09:40:33.631] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms log [09:40:36.181] [info][status][plugin:elasticsearch] Status changed from red to green - Kibana index ready ``` Except one index, which is red, every other index on my ES cluster is green.. and its serving graphs to a Grafana endpoint just fine. ES2 does not have Shield. Any thoughts? or pointers? For starters, I have increased some time out values in kibana.yml. Thanks ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 4, 2015, 3:40am UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/2 "2015-12-04T03:40:55Z")
Anything in the ES logs? ---
**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\ **Post date:** [December 15, 2015, 8:33pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/3 "2015-12-15T20:33:51Z")
Hi @warkolm, Wanted to get back to you after updating my infra. My ES infra now has 8 data nodes, 2 client nodes and 3 master nodes. Kibana 4.3 is pointing to one of the client nodes. I still see the same message and Kibana connection is flapping with the new infra changes. I removed deleted 'red' indices and now, I have: ``` { "cluster_name" : "live", "status" : "green", "timed_out" : false, "number_of_nodes" : 13, "number_of_data_nodes" : 8, "active_primary_shards" : 1734, "active_shards" : 5188, "relocating_shards" : 2, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 3, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 1366, "active_shards_percent_as_number" : 100.0 } ``` I have made sure nothing is populating ES except Marvel (which is what I wanted to use Kibana for). When I shut down my LS2 instance, I did see some shard allocation tracebacks. But will now observe for other logs. I am able to reach the Kibana's /app/marvel URL but the data there does not seem right there. For example, I see all the servers in the cluster show Shards as 0. Perhaps something else that I will investigate and post in the Marvel group, but holding off pending further investigation. Thanks. ---
**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\ **Post date:** [December 15, 2015, 11:13pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/4 "2015-12-15T23:13:02Z")
Interesting observation. I moved Kibana to one of my client nodes and dont see the issue anymore. Perhaps a network issue? ---
**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\ **Post date:** [December 16, 2015, 1:17pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/5 "2015-12-16T13:17:21Z")
Update: spoke too soon. Same issue persists. So dont think its a network issue between the Kibana and the client nodes. Its something else. State of my cluster: ``` { "cluster_name" : "sln-live", "status" : "green", "timed_out" : false, "number_of_nodes" : 14, "number_of_data_nodes" : 9, "active_primary_shards" : 2075, "active_shards" : 6210, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 } ``` Marvel was showing me cluster state, but now I see Marvel is not sending Kibana anything. All dashboards are empty. Any help/thoughts? Place to investigate? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 16, 2015, 9:01pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/6 "2015-12-16T21:01:38Z")
Are all your nodes on the same network? ---
**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\ **Post date:** [December 16, 2015, 9:14pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/7 "2015-12-16T21:14:19Z")
Yeah, they are on the same network. Different subnets though, connected through more than one L2 switches. Thanks. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 16, 2015, 9:45pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/8 "2015-12-16T21:45:42Z")
Then chances are your network is flaky. It may be worth zen increasing timeouts a little to see if it helps. ---
**Author:** ![lukaslehmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukaslehmann/32/6741_2.png) [@lukaslehmann](https://discuss.elastic.co/u/lukaslehmann)\ **Post date:** [December 20, 2015, 2:48pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/9 "2015-12-20T14:48:44Z")
Hi mad\_min We had the same issue, the following solution with setting the memory limitation properly for the kibana node process seems to fix it: > Best regards Lukas ---
**Author:** ![mad\_min](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mad_min/32/5964_2.png) [@mad\_min](https://discuss.elastic.co/u/mad_min)\ **Post date:** [December 27, 2015, 5:43am UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/10 "2015-12-27T05:43:43Z")
Thanks Lukas, This has been running flawlessly thanks to your pointer. We got a bit worried because we took apart parts of our network to figure out if there was any issue with spanning tree or routing loops and didnt find any. Thanks ---
**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:06pm UTC](https://discuss.elastic.co/t/kibana-flapping-between-red-and-green/36328/11 "2017-07-06T14:06:00Z")