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

During discovery, verify connect when sending a rejoin cluster request #6779

Closed
wants to merge 2 commits into from

Conversation

bleskes
Copy link
Contributor

@bleskes bleskes commented Jul 8, 2014

When a master receives a cluster state from another node, it compares the local cluster state with the one it got. If the local one has a higher version, it sends a JoinClusterRequest to the other master to tell it step down. Because our network layer is asymmetric, we need to make sure we're connected before sending.

When a master receives a cluster state from another node, it compares the local cluster state with the one it got. If the local one has a higher version, it sends a JoinClusterRequest to the other master to tell it step down. Because our network layer is asymmetric, we need to make sure we're connected before sending.
});

try {
// make sure we're connect to this node (connect to node exists if we already are
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the comment is not properly phrase? maybe mention that the node might got disconnected?

@kimchy
Copy link
Member

kimchy commented Jul 8, 2014

LGTM except for the comment phrasing

@bleskes
Copy link
Contributor Author

bleskes commented Jul 8, 2014

thx. comment fixed and extended.

@bleskes bleskes closed this in c9b0816 Jul 8, 2014
bleskes added a commit that referenced this pull request Jul 8, 2014
When a master receives a cluster state from another node, it compares the local cluster state with the one it got. If the local one has a higher version, it sends a JoinClusterRequest to the other master to tell it step down. Because our network layer is asymmetric, we need to make sure we're connected before sending.

Closes #6779
@bleskes bleskes deleted the reconnect_when_sending_rejoin branch July 8, 2014 12:43
@jpountz jpountz removed the review label Jul 16, 2014
@clintongormley clintongormley changed the title [Discovery] verify connect when sending a rejoin cluster request Resiliency: During discovery, verify connect when sending a rejoin cluster request Jul 16, 2014
@clintongormley clintongormley added the :Distributed/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure label Jun 7, 2015
@clintongormley clintongormley changed the title Resiliency: During discovery, verify connect when sending a rejoin cluster request During discovery, verify connect when sending a rejoin cluster request Jun 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure >enhancement resiliency v1.3.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants