# SocketTimeoutException: null

**URL:** <https://discuss.elastic.co/t/sockettimeoutexception-null/188433>\
**Category:** Elasticsearch\
**Created:** [July 2, 2019, 4:43am UTC](https://discuss.elastic.co/t/sockettimeoutexception-null/188433 "2019-07-02T04:43:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christopher\_Glantsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christopher_glantsch/32/49138_2.png) [@Christopher\_Glantsch](https://discuss.elastic.co/u/Christopher_Glantsch)\
**Post date:** [July 2, 2019, 4:43am UTC](https://discuss.elastic.co/t/sockettimeoutexception-null/188433/1 "2019-07-02T04:43:50Z")

</div>

I am having a cluster on [elastic.co](http://elastic.co) and I have there basically 5 indexes. 1 of them has many write operations ( like 100 a minute ), where some of them are also bulk inserts.  
the other indexes are mainly there for reading and there are like 50 read operations a minute, but it is just written like a few times a day.

So currently I get about 300 times a day a SocketTimeoutException: null, host not reachable Exception on my Java Client.

Any ideas what I could change in the cluster to fix it or improve it?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 2, 2019, 6:07am UTC](https://discuss.elastic.co/t/sockettimeoutexception-null/188433/2 "2019-07-02T06:07:00Z")

</div>

Do you have monitoring enabled? If so, what does your heap usage look like?

---

<div class="post-metadata">

**Author:** ![Christopher\_Glantsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christopher_glantsch/32/49138_2.png) [@Christopher\_Glantsch](https://discuss.elastic.co/u/Christopher_Glantsch)\
**Post date:** [July 2, 2019, 6:27am UTC](https://discuss.elastic.co/t/sockettimeoutexception-null/188433/3 "2019-07-02T06:27:14Z")

</div>

![22](https://us1.discourse-cdn.com/elastic/original/3X/0/0/00520c7ddace5aa4e926279ddee221ae3430b655.png)

that are the values of the 2 nodes we have

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 2, 2019, 7:14am UTC](https://discuss.elastic.co/t/sockettimeoutexception-null/188433/4 "2019-07-02T07:14:12Z")

</div>

It seems heap is at 75% which is when GC kicks in. If it stays at this level you will need to either reduce heap usage or increase the size of your cluster.

---

<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:** [August 12, 2019, 7:19am UTC](https://discuss.elastic.co/t/sockettimeoutexception-null/188433/6 "2019-08-12T07:19:48Z")

</div>

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