# GET /\_nodes not showing offline nodes

**URL:** <https://discuss.elastic.co/t/get-nodes-not-showing-offline-nodes/178156>\
**Category:** Elasticsearch\
**Created:** [April 24, 2019, 5:31am UTC](https://discuss.elastic.co/t/get-nodes-not-showing-offline-nodes/178156 "2019-04-24T05:31:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chdudfield](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chdudfield](https://discuss.elastic.co/u/chdudfield)\
**Post date:** [April 24, 2019, 5:31am UTC](https://discuss.elastic.co/t/get-nodes-not-showing-offline-nodes/178156/1 "2019-04-24T05:31:38Z")

</div>

I am running Elasticsearch 5.5.2 with 3 nodes in a cluster, one master only and the other two master and data. When i do a "GET /\_nodes" command from within Kibana it returns  
"\_nodes": {  
"total": 3,  
"successful": 3,  
"failed": 0  
}  
which is what i would expect.  
However when i turn one of the nodes off and do the same command it returns  
"\_nodes": {  
"total": 2,  
"successful": 2,  
"failed": 0  
}  
Is this expected behavior and is there a way to force Elasticsearch to search for all three nodes and show an error if one is offline?  
The yml config file has all three nodes configured like discovery.zen.ping.unicast.hosts: ["IP\_ADDRESS\_OR\_HOSTNAME1", "IP\_ADDRESS\_OR\_HOSTNAME2", "IP\_ADDRESS\_OR\_HOSTNAME3"]

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 24, 2019, 8:17am UTC](https://discuss.elastic.co/t/get-nodes-not-showing-offline-nodes/178156/2 "2019-04-24T08:17:40Z")

</div>

> [@chdudfield](#):
>
> Is this expected behavior and is there a way to force Elasticsearch to search for all three nodes and show an error if one is offline?

Yes, that's the expected behaviour. You can use [alerting](https://www.elastic.co/guide/en/elastic-stack-overview/current/xpack-alerting.html) to alert you if the cluster isn't in the state you expect. There's nothing in core Elasticsearch to check this because there's nothing that Elasticsearch itself can do about it.

---

<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 22, 2019, 8:17am UTC](https://discuss.elastic.co/t/get-nodes-not-showing-offline-nodes/178156/3 "2019-05-22T08:17:53Z")

</div>

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