# Elasticsearch - Need to improve cluster performance, (sock hang up) happening a lot

**URL:** <https://discuss.elastic.co/t/elasticsearch-need-to-improve-cluster-performance-sock-hang-up-happening-a-lot/170924>\
**Category:** Elasticsearch\
**Created:** [March 5, 2019, 2:02pm UTC](https://discuss.elastic.co/t/elasticsearch-need-to-improve-cluster-performance-sock-hang-up-happening-a-lot/170924 "2019-03-05T14:02:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jatinseth2007](https://avatars.discourse-cdn.com/v4/letter/j/b19c9b/32.png) [@jatinseth2007](https://discuss.elastic.co/u/jatinseth2007)\
**Post date:** [March 5, 2019, 2:02pm UTC](https://discuss.elastic.co/t/elasticsearch-need-to-improve-cluster-performance-sock-hang-up-happening-a-lot/170924/1 "2019-03-05T14:02:27Z")

</div>

We have Elasticsearch cluster of 3 nodes where 1 node is dedicated master and 2 nodes are dedicated data nodes. we have around 200GB of data on server and heavy \_bulk and \_search operations. The nodes configuration is

```auto
Master node :-
RAM - 8GB
Cores - 4

First Data node :-
RAM - 20GB
Cores - 8

Second Data node :-
RAM - 8GB
Cores - 4

```

We have `5 shards and 1 replica` for all nodes.

We are getting `socket hang up` error very frequently for \_bulk and \_search both, we tried to make all nodes master eligible but it did not work.

---

<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:** [April 2, 2019, 2:02pm UTC](https://discuss.elastic.co/t/elasticsearch-need-to-improve-cluster-performance-sock-hang-up-happening-a-lot/170924/2 "2019-04-02T14:02:35Z")

</div>

Closed on April 2, 2019, 2:02pm UTC

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