CODEWITHSUNDEEP
amazon-web-serviceselasticsearchaws-elasticsearch
Kalvin Klien
Kalvin Klien

Reputation: 921

AWS ElasticSearch - status red

We're having an issue with ElasticSearch on AWS.

The node is in Red Status for couple of hours now. I have no idea how to recover this.

I have tried a few suggestions:

curl -XGET -u 'username:password' 'host:443/_cluster/allocation/explain'

But all of the requests are coming back with:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "master_not_discovered_exception",
        "reason" : null
      }
    ],
    "type" : "master_not_discovered_exception",
    "reason" : null
  },
  "status" : 503
}

The health dashboard is showing this:

enter image description here

Any ideas on how I can recover the instance?

UPDATE:

It looks like one of the nodes has disappeared:

24 hours ago enter image description here

Now: enter image description here

UPDATE:

Maybe there was too much RAM use? How do I fix it? The node is not even listed in the list of nodes. Can I curl a specific node?

enter image description here

UPDATE:

Ended up just re-creating the instance from beginning. Apparently Master nodes is a no-go. You are supposed to have 3 at least as when you have 2 master nodes and one of them crashes, the other one does nothing to restore it.

Upvotes: 0

Views: 303

Answers (1)

warkolm
warkolm

Reputation: 2064

if you are getting the no masters discovered error then there's something pretty wrong with your deployment

you'd need to contact aws support for this, as that is what is managing the node deployment at the end of the day

Upvotes: 2

Related Questions