# MasterNotDiscoveredException
**URL:** https://discuss.elastic.co/t/masternotdiscoveredexception/7260
**Category:** Elasticsearch
**Created:** [April 7, 2012, 10:34pm UTC](https://discuss.elastic.co/t/masternotdiscoveredexception/7260 "2012-04-07T22:34:44Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@LeFinc](https://discuss.elastic.co/u/LeFinc)
#### Post date: [April 7, 2012, 10:34pm UTC](https://discuss.elastic.co/t/masternotdiscoveredexception/7260/1 "2012-04-07T22:34:44Z")
Hi everybody,
I've been running a 2-node elasticsearch cluster for the last couple of months with a total of around 1TB of indexed data.
Today, during heavy load, both clusters became unresponsive. I brought Node 1 down with a kill (perhaps not a good thing to do in hindsight)
Node 2 is not responding to kill; although the server no longer listens on 9200, the process is hanging on even though no disk I/O appears to be taking place.
I can bring Node 1 back up, so that 9200 responds again with the usual message. However, when checking for cluster health, I get the following error:
[http://192.168.1.69:9200/\_cluster/health](http://192.168.1.69:9200/_cluster/health)
=\>
{"error":"MasterNotDiscoveredException[waited for [30s]]","status":503}
and test search gives me
[http://192.168.1.69:9200/\_search?pretty=1](http://192.168.1.69:9200/_search?pretty=1)
=\>
{
"error" : "ClusterBlockException[blocked by: [SERVICE\_UNAVAILABLE/1/state not recovered / initialized];[SERVICE\_UNAVAILABLE/2/no master];]",
"status" : 503
}
Is there anything I can do to recover my data or have I messed this up for good? At the moment, neither node responds to shutdown via Shutdown API either.
Thanks for your help!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 3:33am UTC](https://discuss.elastic.co/t/masternotdiscoveredexception/7260/2 "2017-07-06T03:33:18Z")