# Timeout in Elastic cluster:monitor/nodes/stats

**URL:** <https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043>\
**Category:** Elasticsearch\
**Created:** [May 23, 2018, 7:02pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043 "2018-05-23T19:02:34Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [May 23, 2018, 7:02pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/1 "2018-05-23T19:02:34Z")

</div>

Hello - we are getting a Timeout calling the /\_cat/indexes API - though we're able to call all other APIs ok. The exception we're getting is a cluster:monitor/nodes/stats Timeout in the logs. How do we debug this to see where the problem could lie?

> _[2018-05-23T18:29:47,964][DEBUG][o.e.a.a.c.n.s.TransportNodesStatsAction] [ip-10-111-111-1] failed to execute on node [avcd]_  
> _org.elasticsearch.transport.ReceiveTimeoutTransportException: [ip-10-211-211-1][10.200.187.133:9300][cluster:monitor/nodes/stats[n]] request\_id [4088993] timed out after [15000ms]_

**PS : Would individually restarting each node in the aws cluster INCLUDING the Coordinating Node help?**

This is our cluster information

```
{
    "cluster_name": "prod-application-cluster",
    "status": "green",
    "timed_out": false,
    "number_of_nodes": 7,
    "number_of_data_nodes": 5,
    "active_primary_shards": 281,
    "active_shards": 562,
    "relocating_shards": 0,
    "initializing_shards": 0,
    "unassigned_shards": 0,
    "delayed_unassigned_shards": 0,
    "number_of_pending_tasks": 0,
    "number_of_in_flight_fetch": 0,
    "task_max_waiting_in_queue_millis": 0,
    "active_shards_percent_as_number": 100
}

```

---

<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:** [May 23, 2018, 7:05pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/2 "2018-05-23T19:05:56Z")

</div>

What is the specification of the hardware the cluster is using?

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [May 23, 2018, 7:08pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/3 "2018-05-23T19:08:03Z")

</div>

5 m5.4xlarge Data/Master Nodes !  
2 m5 large Coodinating Nodes!

PS : We've been using this successfully for the past 6 months - this is the first time this has ever happened

---

<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:** [May 23, 2018, 7:11pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/4 "2018-05-23T19:11:52Z")

</div>

Are there any report about long GC in the Elasticsearch logs? Any errors reported?

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [May 23, 2018, 7:13pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/5 "2018-05-23T19:13:42Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> Are there any report about long GC in the Elasticsearch logs? Any errors reported?

Just the errors I posted in the OP. I didn't see any GC related errors.

---

<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:** [May 23, 2018, 7:15pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/6 "2018-05-23T19:15:29Z")

</div>

Then I am not sure what could be going on...

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [May 23, 2018, 7:48pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/7 "2018-05-23T19:48:01Z")

</div>

Would restarting all the nodes individually help? Also - is the number of shards excessively high?

---

<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 20, 2018, 7:48pm UTC](https://discuss.elastic.co/t/timeout-in-elastic-cluster-monitor-nodes-stats/133043/8 "2018-06-20T19:48:01Z")

</div>

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