# ES5.5 got red, and no way to find out which node got error

**URL:** <https://discuss.elastic.co/t/es5-5-got-red-and-no-way-to-find-out-which-node-got-error/99263>\
**Category:** Elasticsearch\
**Created:** [September 4, 2017, 9:16am UTC](https://discuss.elastic.co/t/es5-5-got-red-and-no-way-to-find-out-which-node-got-error/99263 "2017-09-04T09:16:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_ax](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@John\_ax](https://discuss.elastic.co/u/John_ax)\
**Post date:** [September 4, 2017, 9:16am UTC](https://discuss.elastic.co/t/es5-5-got-red-and-no-way-to-find-out-which-node-got-error/99263/1 "2017-09-04T09:16:51Z")

</div>

HI,I was using ES5.5, with hot-warn architecture, now he got red,:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/0/a03b84a7f63d5161417574c21ec9ebb691403df1.png)

`curl xxxx:9400/_cat/nodes` just block for a long time and no way to find out which node GOT out of memory.

---

<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:** [September 4, 2017, 9:19am UTC](https://discuss.elastic.co/t/es5-5-got-red-and-no-way-to-find-out-which-node-got-error/99263/2 "2017-09-04T09:19:30Z")

</div>

Are you not using the default 9200 port for the Elasticsearch HTTP interface?

---

<div class="post-metadata">

**Author:** ![John\_ax](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@John\_ax](https://discuss.elastic.co/u/John_ax)\
**Post date:** [September 4, 2017, 10:15am UTC](https://discuss.elastic.co/t/es5-5-got-red-and-no-way-to-find-out-which-node-got-error/99263/3 "2017-09-04T10:15:34Z")

</div>

no,the http port is 9400.  
I also got this:

```auto
[2017-09-04T18:13:16,395][ERROR][o.e.x.w.e.ExecutionService] [BrSJ2NM] failed to update watch record [dBSYPniQQfmLC89qwijyLg_elasticsearch_cluster_status_bb6644d9-6233-4d2a-9e90-67ec5e19e17a-2017-09-04T10:12:46.308Z]

```

what's that mean ,and how to fix this?  
the x-pack monitor data is gone after I restart all the `warm` nodes and increase the JVM memory to 30GB. the master log telling:

```auto
[2017-09-04T18:24:16,759][DEBUG][o.e.a.a.i.m.p.TransportPutMappingAction] [BrSJ2NM] failed to put mappings on indices [[[.watcher-history-3-2017.09.04/EOVPwPpuRIeJnUTfXfmWNw]]], type [watch_record]

```

maybe I should delete the watcher?  
I think ES should figure out how to improve the maintenance system since the JVM out of memory is inevitable.

---

<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:** [October 2, 2017, 10:17am UTC](https://discuss.elastic.co/t/es5-5-got-red-and-no-way-to-find-out-which-node-got-error/99263/5 "2017-10-02T10:17:31Z")

</div>

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