# Failed to execute on node \[YK3h1SM5SZW2K-JloBdVCg\]

**URL:** <https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252>\
**Category:** Elasticsearch\
**Created:** [May 2, 2018, 1:14pm UTC](https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252 "2018-05-02T13:14:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vincentduan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincentduan/32/30691_2.png) [@vincentduan](https://discuss.elastic.co/u/vincentduan)\
**Post date:** [May 2, 2018, 1:15pm UTC](https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252/1 "2018-05-02T13:15:00Z")

</div>

I am using `curl -H "Content-Type: application/x-ndjson" -XPOST http://192.168.1.102:9200/myindex/mytype/_bulk --data-binary @file` command to import json file into ES cluster.  
my master nodes contains : [192.168.1.101, 192.168.1.102, 192.168.1.103]  
my data nodes contains: [192.168.1.105, 192.168.1.106, 192.168.1.107, 192.168.1.108].  
the master log shows here:

```auto
failed to excute on node [YK3h1SM5SZW2K-JloBdVCg]
org.elasticsearch.transport.ReceiveTimeoutTransportException: [data5][192.168.1.108:9300][cluster:monitor/nodes/stats[n]] request_id [19314] timed out after [15001ms]
    at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:982)
...
...
Received response for a request that has timed out, sent [25237ms] ago, timed out [10236] ago, action [cluster: monitor/nodes/stats[n]], node

```

THE EXCEPTIONS are random appearance, sometimes it can process success and es cluster is GREEN , sometimes some of my data nodes get crashed.

I am not sure it appeared because of low memory ,as I use `free -lh` to show the memory status ,found only 200MB FREE (total 64GB)

Anybody could give me some hints? 👩🏻

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [May 2, 2018, 1:29pm UTC](https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252/2 "2018-05-02T13:29:26Z")

</div>

That looks like monitoring failing to gather statistics about node performance in a timely fashion.  
My guess is these data nodes are running hot? Are you seeing GC warnings in their log files?

---

<div class="post-metadata">

**Author:** ![vincentduan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vincentduan/32/30691_2.png) [@vincentduan](https://discuss.elastic.co/u/vincentduan)\
**Post date:** [May 2, 2018, 1:38pm UTC](https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252/3 "2018-05-02T13:38:07Z")

</div>

THANKS FOR YOUR APPLY.  
I am sure I can see many gc overhead in all of my nodes log file.  
And my curl bulk command process about 300MB json file at one time, should I cut it into more split file?

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [May 2, 2018, 1:39pm UTC](https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252/4 "2018-05-02T13:39:50Z")

</div>

> [@vincentduan](#):
>
> should I cut it into more split file?

Yes, that would certainly help.

---

<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:** [May 30, 2018, 1:39pm UTC](https://discuss.elastic.co/t/failed-to-execute-on-node-yk3h1sm5szw2k-jlobdvcg/130252/5 "2018-05-30T13:39:52Z")

</div>

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