Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cluster broken after switches upgrade #9495

Closed
jbdamiano opened this issue Jan 30, 2015 · 1 comment
Closed

cluster broken after switches upgrade #9495

jbdamiano opened this issue Jan 30, 2015 · 1 comment

Comments

@jbdamiano
Copy link

Hello,

We have actually 7 nodes. We use elasticsearch 1.3.2.

We are configured in unicast mode with a minimum consistency of 4
Two days ago, in the night, network team has done a switches firmware upgrade of all production switches.

The result of this upgrade has been catastrophic for the cluster.
The cluster has been split in two parts with some node in first and second part

Node 3 and Node 5 was master together

Node 3 with Node 1, Node3 and Node 6
Node 5 with Node 1, Node2, Node4, Node 5, Node 6 and Node 7

Fortunately we have a second cluster on other lab which the same data and we have been able to do a snapshot/restore from this cluster to the first one after a rolling restart.

And don't understand how a switch upgrade, and a connectivity lost, can result of a corrupted cluster allocation.

Regards,

@bleskes
Copy link
Contributor

bleskes commented Jan 30, 2015

@GOUKETSU that's very unfortunate. This happens because of #2488 which was fixed with 1.4.0 . I suggest you upgrade as soon as you can.

I'm closing this as duplicate. Feel free to comment if you have any question.

@bleskes bleskes closed this as completed Jan 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants