[Discovery] verify we have a master after a successful join request #6969

Closed
wants to merge 1 commit into
from

Projects

None yet

3 participants

@bleskes
Member
bleskes commented Jul 22, 2014

After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

@bleskes bleskes [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.
bb14455
@martijnvg
Member

LGTM

@bleskes bleskes added a commit that referenced this pull request Jul 22, 2014
@bleskes bleskes [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
07c8510
@bleskes bleskes closed this Jul 22, 2014
@bleskes bleskes deleted the bleskes:join_with_failed_cs_publishing branch Jul 22, 2014
@jpountz jpountz removed the review label Jul 24, 2014
@bleskes bleskes added a commit that referenced this pull request Aug 4, 2014
@bleskes @martijnvg bleskes + martijnvg [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
0e9873b
@bleskes bleskes added a commit that referenced this pull request Aug 5, 2014
@bleskes @martijnvg bleskes + martijnvg [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
a3f9f71
@bleskes bleskes added a commit that referenced this pull request Aug 14, 2014
@bleskes @martijnvg bleskes + martijnvg [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
40ff82a
@bleskes bleskes added a commit that referenced this pull request Aug 22, 2014
@bleskes bleskes [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
a671865
@bleskes bleskes added a commit that referenced this pull request Aug 23, 2014
@bleskes bleskes [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
8ba7fe5
@bleskes bleskes added a commit that referenced this pull request Aug 27, 2014
@bleskes bleskes [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
cccd060
@bleskes bleskes added a commit to bleskes/elasticsearch that referenced this pull request Sep 1, 2014
@bleskes bleskes [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
07aad20
@bleskes bleskes added a commit that referenced this pull request Sep 8, 2014
@bleskes @areek bleskes + areek [Discovery] verify we have a master after a successful join request
After master election, nodes send join requests to the elected master. Master is then responsible for publishing a new cluster state which sets the master on the local node's cluster state. If something goes wrong with the cluster state publishing, this process will not successfully complete. We should check it after the join request returns and if it failed, retry pinging.

Closes #6969
40911c6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment