# \[cluster:monitor/nodes/stats\[n\]\] timed out

**URL:** <https://discuss.elastic.co/t/cluster-monitor-nodes-stats-n-timed-out/377322>\
**Category:** Elasticsearch\
**Created:** [April 21, 2025, 5:31am UTC](https://discuss.elastic.co/t/cluster-monitor-nodes-stats-n-timed-out/377322 "2025-04-21T05:31:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZaynJiang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zaynjiang/32/142742_2.png) [@ZaynJiang](https://discuss.elastic.co/u/ZaynJiang)\
**Post date:** [April 21, 2025, 5:31am UTC](https://discuss.elastic.co/t/cluster-monitor-nodes-stats-n-timed-out/377322/1 "2025-04-21T05:31:44Z")

</div>

I encountered exactly the same problem. Both the thread stack and the logs are identical. This issue has been closed, but it remains unsolved.

> [@Action \[cluster:monitor/nodes/stats\[n\]\] timed out](https://discuss.elastic.co/t/action-cluster-monitor-nodes-stats-n-timed-out/312818):
>
> I can't take the log file out. Logs says: Received response for a request that as timed out, sent [xxx/xxx] ago..... tells that a timeout occurred when the master tries to collecting node stats info from one particular data node, and the time waited for response increased from 10s to about 20min during about 1.5hour. In the meanwhile, the data node worked all fine, and the cluster remains green, and all read/write actions run perfectly. I had to restart the data node to fix this, and it …