# Elasticsearch timeout after 30000ms

**URL:** <https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126>\
**Category:** Elasticsearch\
**Created:** [May 28, 2019, 2:30pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126 "2019-05-28T14:30:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![matheusribeirogarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matheusribeirogarcia/32/44363_2.png) [@matheusribeirogarcia](https://discuss.elastic.co/u/matheusribeirogarcia)\
**Post date:** [May 28, 2019, 2:30pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/1 "2019-05-28T14:30:39Z")

</div>

Hello everyone, basically i'm importing several totalized indices into one indice, but after sometime I get this timeout, and it also totally freezes my elastic cluster.

I'm using a RestHighLevelClient like this:

```
	    RestHighLevelClient client = new RestHighLevelClient(
				RestClient.builder(new HttpHost(server, 9200, "http")));
```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 28, 2019, 2:39pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/2 "2019-05-28T14:39:18Z")

</div>

Anything in elasticsearch server logs?

What is the output of:

```auto
GET /
GET /_cat/nodes?v
GET /_cat/health?v

```

If some outputs are too big, please share them on [gist.github.com](http://gist.github.com) and link them here.

---

<div class="post-metadata">

**Author:** ![matheusribeirogarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matheusribeirogarcia/32/44363_2.png) [@matheusribeirogarcia](https://discuss.elastic.co/u/matheusribeirogarcia)\
**Post date:** [May 28, 2019, 2:43pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/3 "2019-05-28T14:43:33Z")

</div>

Should I re-run my agent to make it timeout again?

Because I restarted it and there's nothing really out of normal is these GETs

```
GET /
{
  "name": "vffr_QL",
  "cluster_name": "cluster_migration",
  "cluster_uuid": "2hQjSvZ-RRyPzjNaLYDU7g",
  "version": {
    "number": "6.4.0",
    "build_flavor": "default",
    "build_type": "tar",
    "build_hash": "595516e",
    "build_date": "2018-08-17T23:18:47.308994Z",
    "build_snapshot": false,
    "lucene_version": "7.4.0",
    "minimum_wire_compatibility_version": "5.6.0",
    "minimum_index_compatibility_version": "5.0.0"
  },
  "tagline": "You Know, for Search"
}
GET /_cat/nodes?v
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
127.0.0.1 58 99 17 0.20 0.54 0.85 mdi * vffr_QL

GET /_cat/health?v
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1559054584 14:43:04 cluster_migration yellow 1 1 377 377 0 0 348 0 - 52.0%
```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 28, 2019, 2:52pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/4 "2019-05-28T14:52:31Z")

</div>

How much HEAP is allocated to your node?

Also could you use a more recent version than `6.4.0`?

---

<div class="post-metadata">

**Author:** ![matheusribeirogarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matheusribeirogarcia/32/44363_2.png) [@matheusribeirogarcia](https://discuss.elastic.co/u/matheusribeirogarcia)\
**Post date:** [May 28, 2019, 2:57pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/5 "2019-05-28T14:57:24Z")

</div>

> Disk Available
> 
> 45.71%
> 
> 359.5 GB / 786.4 GB
> 
> JVM Heap
> 
> 61.60%
> 
> 2.4 GB / 4.0 GB

Unfortunatelly i'm not able to change my version.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 28, 2019, 3:21pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/6 "2019-05-28T15:21:16Z")

</div>

You probably have too many shards per node.

May I suggest you look at the following resources about sizing:

[https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)

> **[How many shards should I have in my Elasticsearch cluster?](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**
>
> If you are looking for practical guidelines around how many indices and shards to have in your cluster, this blog post will help you avoid common pitfalls.

https://www.slideshare.net/slideshow/embed_code/key/vR0XKDq4TGa77z

And [https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right)

---

<div class="post-metadata">

**Author:** ![matheusribeirogarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matheusribeirogarcia/32/44363_2.png) [@matheusribeirogarcia](https://discuss.elastic.co/u/matheusribeirogarcia)\
**Post date:** [May 28, 2019, 3:22pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/7 "2019-05-28T15:22:47Z")

</div>

I'll check it, thanks

---

<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:** [June 25, 2019, 3:22pm UTC](https://discuss.elastic.co/t/elasticsearch-timeout-after-30000ms/183126/8 "2019-06-25T15:22:54Z")

</div>

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