We are running an elasticsearch cluster with three nodes on AWS EC2. Each node uses the AWS Cloud Plugin to discover each other. In front of the cluster, we put a private elastic load balancer (ELB), so our rails apps can talk to that ELB to find the elasticsearch cluster. Currently we are using elasticsearch version
Regularly - but not often - we receive status code
GatewayTimeout from the ELB.
What's the ideal
IdleTimeout of the ELB, which is used in front of an elasticsearch cluster?
AWS describes in its Developer Guide how to set the idle timeout. The only thing I found concerning
keep_alive timeouts in elasticsearch is in this ThreadPool source code. But if I configure the
IdleTimeout of the ELB to 29 seconds the
504 error still occurs.
So what's the
keep_alive value of elasticsearch?