Not all master election related cluster state update task use Priority.IMMEDIATE #7718
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…use Priority.IMMEDIATE Most notably the elected_as_master task should run as soon as possible. This is an issue as node join request do use `Priority.IMMEDIATE` and can be unjustly rejected.
|
LGTM |
bleskes
added a commit
that referenced
this pull request
Sep 15, 2014
…use Priority.IMMEDIATE Most notably the elected_as_master task should run as soon as possible. This is an issue as node join request do use `Priority.IMMEDIATE` and can be unjustly rejected. Closes #7718
bleskes
added a commit
that referenced
this pull request
Sep 15, 2014
…use Priority.IMMEDIATE Most notably the elected_as_master task should run as soon as possible. This is an issue as node join request do use `Priority.IMMEDIATE` and can be unjustly rejected. Closes #7718
clintongormley
added
the
:Distributed/Discovery-Plugins
clintongormley
changed the title
mute
pushed a commit
to mute/elasticsearch
that referenced
this pull request
Jul 29, 2015
…use Priority.IMMEDIATE Most notably the elected_as_master task should run as soon as possible. This is an issue as node join request do use `Priority.IMMEDIATE` and can be unjustly rejected. Closes elastic#7718
This was referenced Oct 25, 2021
jkakavas
added a commit
that referenced
this pull request
Oct 27, 2021
This change introduces a CLI tool that can be run directly after installation time in packaged installations, to allow for a node that was auto-configured to be the initial node of a cluster during installation ( default installation behavior) to be reconfigured to join an existing cluster, using an enrollment token. The use of this tool presumes that the user has the appropriate permissions to read/write to the installation dirs and that this node has not been yet started, i.e. this tool is run directly after installation. It is destructive, as it removes existing security auto-configuration, and as such it requires an explicit verification from the user. This is a follow-up to #7718.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Most notably the elected_as_master task should run as soon as possible. This is an issue as node join request do use
Priority.IMMEDIATEand can be unjustly rejected.