# Multiple issues with ELK

**URL:** <https://discuss.elastic.co/t/multiple-issues-with-elk/63667>\
**Category:** Kibana\
**Created:** [October 22, 2016, 6:18pm UTC](https://discuss.elastic.co/t/multiple-issues-with-elk/63667 "2016-10-22T18:18:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![davecs](https://avatars.discourse-cdn.com/v4/letter/d/43a26b/32.png) [@davecs](https://discuss.elastic.co/u/davecs)\
**Post date:** [October 22, 2016, 6:18pm UTC](https://discuss.elastic.co/t/multiple-issues-with-elk/63667/1 "2016-10-22T18:18:40Z")

</div>

Hi Everyone-

Ok i will try to be as clear as possible with this.

i have 3 VM with CentOs 7 like this: (1 Elasticsearch Cluster of 3 nodes, 2 master eligible and data, and 1 node client)

1. Elasticsearch ( 12GB of RAM, 3 CPUs - 2 cores per socket- , 500 GB HDD)
2. Elasticsearch ( 12GB of RAM, 3 CPUs - 2 cores per socket- , 500 GB HDD)
3. Kibana - nginx reverse proxy-, Logstash, Elasticsearch node client (16GB of RAM, 2 CPUs -1 core per socket- , 500GB HHD, 154 GB HDD)

the network adapter are 1GB, full duplex, autonegotiation.

all the elasticsearch cluster machines are configured with

MAX\_LOCKED\_MEMORY=unlimited  
LimitMEMLOCK=infinity  
bootstrap.memory\_lock: true  
ES\_HEAP\_SIZE=8g (6g in the node client)  
network.host: [_eno16777984_, _local_]  
discovery.zen.ping.unicast.hosts: ["node 1 address", "node 2 address", "node client adress"]  
Shards 5\*2

i have Kopf installed to check the cluster health, so when i send queries (1 day of data logs) this is what i can observe:

the heap: 60%  
cpu: 90% (red state)  
disk: 75% space free  
Load: is red

i tried to use the Elasticsearch with 3 CPUs -3 cores per socket- got same result.....

In kibana i always get this

Error: Bad Gateway  
at respond (http://**/bundles/kibana.bundle.js?v=10146:78604:16)  
at checkRespForFailure (http://**/bundles/kibana.bundle.js?v=10146:78567:8)  
at http://**/bundles/kibana.bundle.js?v=10146:77185:8  
at processQueue (http://**/bundles/commons.bundle.js?v=10146:42452:29)  
at http://**/bundles/commons.bundle.js?v=10146:42468:28  
at Scope.$eval (http://**/bundles/commons.bundle.js?v=10146:43696:29)  
at Scope.$digest (http://**/bundles/commons.bundle.js?v=10146:43507:32)  
at Scope.$apply (http://**/bundles/commons.bundle.js?v=10146:43804:25)  
at done (http://**/bundles/commons.bundle.js?v=10146:38253:48)  
at completeRequest (http://**/bundles/commons.bundle.js?v=10146:38451:8)

i check the logs and just showed me an issue with babelcache.json  
but i fixed it with chmod o+w /opt/kibana/optimize/.babelcache.json

and Request Timeout after 30000ms

this is what i modified with different values after i saw a couple of people having the same issue and got it fix:

threadpool.search.queue\_size:  
elasticsearch.requestTimeout:

sometimes rebooting the entire cluster makes everything better and smoother but just for a couple of minutes

i am a completly noob in this universe of the elastic products, so please bear with me!

thank you for your patiente and time.

---

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [October 27, 2016, 1:38pm UTC](https://discuss.elastic.co/t/multiple-issues-with-elk/63667/2 "2016-10-27T13:38:37Z")

</div>

Is the problem you're trying to solve the `Error: Bad Gateway` ?

Is your nginx proxy between Kibana and Elasticsearch? Or in front of Kibana? What is the purpose in your case for nginx there?

Regards,  
Lee

---

<div class="post-metadata">

**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:35pm UTC](https://discuss.elastic.co/t/multiple-issues-with-elk/63667/3 "2017-07-06T13:35:30Z")

</div>