# We are having performance issue in Elasticsearch/Kibana after migrating to another server host **URL:** \ **Category:** Kibana\ **Created:** [July 19, 2020, 5:14am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771 "2020-07-19T05:14:07Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![\_kyllr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/_kyllr/32/27610_2.png) [@\_kyllr](https://discuss.elastic.co/u/_kyllr)\ **Post date:** [July 19, 2020, 5:14am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/1 "2020-07-19T05:14:07Z")
Hello, We are having issue in Kibana. We have AWS Proxy and Kibana 7.1 setup in the same server. After migrating both to another server host and make it live in the load balancer, we are facing request timeout issue when accessing our Kibana application. ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4c3c95a0530b1bc0b121c88ca099a4a51949ccf5.png) Though when using the old server back in the load balancer, it works perfectly fine. Does anyone know why this is happening? Any related information will be appreciated. Thank you! PS: Both servers has the same specification. By the way, here are the settings that we have: **AWS Elasticsearch Proxy** aws-es-proxy-0.9-windows-amd64.exe -endpoint "https://vpc\_endpoint " -listen "127.0.0.1:9230" **Kibana.yml** server.port: 5609 server.host: "x.x.x.x" server.basePath: "/7.1/kibana" elasticsearch.hosts: "[http://127.0.0.1:9230/](http://127.0.0.1:9230/)" elasticsearch.ssl.verificationMode: none elasticsearch.requestTimeout: 300000 ---
**Author:** ![\_kyllr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/_kyllr/32/27610_2.png) [@\_kyllr](https://discuss.elastic.co/u/_kyllr)\ **Post date:** [July 20, 2020, 11:21am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/2 "2020-07-20T11:21:05Z")
Anyone could help on this issue? ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [July 20, 2020, 8:09pm UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/3 "2020-07-20T20:09:20Z")
Kibana is timing out communicating with Elasticsearch. What is between Kibana and Elasticsearch? Is there also a proxy there? ---
**Author:** ![\_kyllr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/_kyllr/32/27610_2.png) [@\_kyllr](https://discuss.elastic.co/u/_kyllr)\ **Post date:** [July 21, 2020, 12:34am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/4 "2020-07-21T00:34:53Z")
We only used proxy in Elasticsearch. We defined elasticsarch.hosts in kibana.yml to connect our Kibana to Elasticsarch, Does it ES having the main cause here? ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [July 21, 2020, 3:19am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/5 "2020-07-21T03:19:45Z")
> [@\_kyllr](#): > > We only used proxy in Elasticsearch. To confirm, is `elasticsearch.hosts` pointing to a proxy, or an Elasticsearch node? If it's a proxy, can you try changing it to point directly to an Elasticsearch node to rule out the issue being the proxy? Other than being network related, it could be that Elasticsearch is far too overwhelmed to serve any requests. What is the health of the cluster at this time? Does the [Cluster Health](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html) ever go red during this time? ---
**Author:** ![\_kyllr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/_kyllr/32/27610_2.png) [@\_kyllr](https://discuss.elastic.co/u/_kyllr)\ **Post date:** [July 21, 2020, 3:57am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/6 "2020-07-21T03:57:41Z")
Hi @tylersmalley, Can you provide an Elasticsearch node sample? I believe elasticsearch.hosts is pointing to a proxy. We are currently pointing on the server host that doesn't have the issue. Here is the status of the Cluster Health right now. > { > "cluster\_name" : "xxxxxx:xxx-xxxx-prod", > "status" : "green", > "timed\_out" : false, > "number\_of\_nodes" : 23, > "number\_of\_data\_nodes" : 20, > "discovered\_master" : true, > "active\_primary\_shards" : 680, > "active\_shards" : 1360, > "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 > } I'll try to point ES/Kibana in the server host having the said issue and check the Cluster Health Status. Thanks for helping in this matter. ---
**Author:** ![\_kyllr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/_kyllr/32/27610_2.png) [@\_kyllr](https://discuss.elastic.co/u/_kyllr)\ **Post date:** [July 22, 2020, 6:01am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/7 "2020-07-22T06:01:16Z")
![image](https://us1.discourse-cdn.com/elastic/original/3X/d/0/d065d0348fc9343e575ec5b3b342b0bbae7e5300.png) Uploading here the status of the Cluster. ---
**Author:** ![\_kyllr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/_kyllr/32/27610_2.png) [@\_kyllr](https://discuss.elastic.co/u/_kyllr)\ **Post date:** [July 23, 2020, 2:49am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/8 "2020-07-23T02:49:29Z")
Could anyone help me with this? This is a production issue. Here's the comparison of the instances where we're running Proxy and Kibana. Old - which having no issue Windows Server 2012 R2 Processor: Inter(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz 2.90 GHz Installed memory (RAM): 30.0 GB System type: 64-bit OS, x64-based processor Virtual processor: 16 New - which has the issue Windows Server 2016 Processor: Inter(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz 3.00 GHz Installed memory (RAM): 31.0 GB System type: 64-bit OS, x64-based processor Virtual processor: 8 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 20, 2020, 2:49am UTC](https://discuss.elastic.co/t/we-are-having-performance-issue-in-elasticsearch-kibana-after-migrating-to-another-server-host/241771/9 "2020-08-20T02:49:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.