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.

Sign up for GitHub

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

Jump to bottom

Zen Discovery: ungraceful shutdown of the master and start of replacement node might cause the cluster not to elect a new master #200

Closed
kimchy opened this issue Jun 1, 2010 · 1 comment
Closed

Zen Discovery: ungraceful shutdown of the master and start of replacement node might cause the cluster not to elect a new master #200

kimchy opened this issue Jun 1, 2010 · 1 comment
Labels
>bug v0.09.0

Comments

@kimchy
Copy link
Member

kimchy commented Jun 1, 2010

If killing -9 the master, and then starting a new node right away on the same box might cause the cluster to get into a state where a new master is not elected. This is because the new node will use the same port and it will be considered as the failed node.
@kimchy
Copy link
Member Author

kimchy commented Jun 1, 2010

Zen Discovery: ungraceful shutdown of the master and start of replacement node might cause the cluster not to elect a new master, closed by a7ad295.

@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
@jakommo
Merge pull request elastic#200 from jakommo/master
9dc21d4 
Conditional for checking if shield is in the feature list, did not work.
Closes elastic#190
@Hailei Hailei mentioned this issue Mar 16, 2021
Closed
@FabienZa FabienZa mentioned this issue Nov 16, 2022
Closed
costin pushed a commit that referenced this issue Dec 6, 2022
@bpintea
Merge pull request #200 from elastic/main
5633076 
🤖 ESQL: Merge upstream
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@drawlerr
Fix exception on invocation with no args (elastic#200)
21a81af
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.09.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy