Hello,
We recently had an issue adding a node to our Elastic Search cluster, and
would be interested in anything I could do to troubleshoot the issue.
We currently have a 2 node cluster that has been running for some time. I
am looking to add a third node to this cluster. All nodes are running on
AWS, and we use ec2 discovery to allow nodes to discover each other:
discovery:
type: ec2
ec2:
groups: vpc-elastic-search4
Both nodes are part of the security group vpc-elastic-search4.
We attempted to bring up a new node that was an AMI of one of the existing
two nodes, and recreated the partition we utilized for storing index data.
We then added the node to the vpc-elastic-search4 security group.
However, when we brought up the node, something strange happened causing us
to abort the attempt. The status of the nodes showed:
Node1 - Status: green, number of nodes: 2
Node2 - Status: yellow: number of nodes: 2 (relocating and initializing
shards)
Node3 - Status: yellow: number of nodes: 2 (relocating and initializing
shards) - This was the new node.
We immediately shutdown node 3. After that point, Node 2 had the number of
nodes set to 1, while Node 1 still showed 2 still showed green.
We shut down and restarted Node2, and it properly recovered from Node 1.
It almost seems that starting Node 3 caused Node 2 to become partitioned
from Node 1, without Node 1 also reflecting that change? However, that is
a guess on my part. I'm reluctant to try again for fear of causing damage.
We are running 0.90.11. Any insight would be appreciated,
-Mike
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/8c86a371-d955-4fe9-b714-4383b075d9d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
