Connection pool does not look for other hosts in the config when a connection goes down about elasticsearch-js HOT 3 CLOSED

Sounds like before ES2 goes down the client sniffs the cluster and sees that it's made up of one node (ES2), causing it to remove all other connections. Then, when ES2 goes down, the client keeps trying to connect to the only node it knows of (EC2).

The simplest answer is probably to add nodes to your cluster, this could prevent your entire cluster from falling over and therefore prevent this issue.

If plan to keep your cluster at two nodes, I'd suggest disabling sniffing. With sniffing disabled, connections won't be removed dynamically and your original host list will always be used.

Finally, increasing the sniffInterval should make this less likely but it won't actually prevent it from happening.

from elasticsearch-js.

Yes, That works. Thank you. 👍
Shouldn't the sniffInterval update the list of hosts and add to the connectionPool?

from elasticsearch-js.

Yes, but it relies on the cluster to define the current list of nodes.

from elasticsearch-js.