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.
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"
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 ever go red during this time?
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
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.