Connection Timeout Settings for the Java Client


(Manish Pandit) #1

We are running ElasticSearch with 4 nodes, and accessing it with the
Java Client. Last night one of the nodes became unresponsive
(basically curl to :9200/_status froze). Other nodes were just fine. I
was wondering if there is a way to set a connection timeout at the
driver level - or configure the driver in a way where it can fail over
under such situations. I am aware of the setTimeout in
SearchRequestBuilder, but as far as I understand thats to control how
long the actual search takes, not including the connection time.
Please let me know - I appreciate your help!

-cheers,
Manish


(Shay Banon) #2

The node will be detected as unresponsive and removed (both when using
TransportClient and NodeClient). The default connect timeout is 30 seconds.

On Wed, Jan 18, 2012 at 8:41 PM, Manish Pandit pandit.manish@gmail.comwrote:

We are running ElasticSearch with 4 nodes, and accessing it with the
Java Client. Last night one of the nodes became unresponsive
(basically curl to :9200/_status froze). Other nodes were just fine. I
was wondering if there is a way to set a connection timeout at the
driver level - or configure the driver in a way where it can fail over
under such situations. I am aware of the setTimeout in
SearchRequestBuilder, but as far as I understand thats to control how
long the actual search takes, not including the connection time.
Please let me know - I appreciate your help!

-cheers,
Manish


(system) #3