# java.net.SocketTimeoutException: Read timed out when nodes leave the cluster

**URL:** <https://discuss.elastic.co/t/java-net-sockettimeoutexception-read-timed-out-when-nodes-leave-the-cluster/356701>\
**Category:** Elasticsearch\
**Created:** [April 3, 2024, 3:13pm UTC](https://discuss.elastic.co/t/java-net-sockettimeoutexception-read-timed-out-when-nodes-leave-the-cluster/356701 "2024-04-03T15:13:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chuck\_Reynolds](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chuck_reynolds/32/103607_2.png) [@Chuck\_Reynolds](https://discuss.elastic.co/u/Chuck_Reynolds)\
**Post date:** [April 3, 2024, 3:13pm UTC](https://discuss.elastic.co/t/java-net-sockettimeoutexception-read-timed-out-when-nodes-leave-the-cluster/356701/1 "2024-04-03T15:13:31Z")

</div>

I'm seeing a lot of SocketTimeout read errors when nodes leave the cluster.  
The nodes return with in a few minutes of leaving.

The cluster has a primary and 1 replica.

We are using Elasticsearch 7.16.3 in Kubernetes and when nodes get reclaimed which seems to happen often then we see a bunch of the SocketTimeout errors.

The timeout is set to 2500ms which seems to be a very long time.

We are talking to the cluster using a restful call.

Thanks for any help.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 1, 2024, 3:13pm UTC](https://discuss.elastic.co/t/java-net-sockettimeoutexception-read-timed-out-when-nodes-leave-the-cluster/356701/2 "2024-05-01T15:13:45Z")

</div>

Closed on May 1, 2024, 3:13pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.