-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fix issue that deprecated setting 'cluster.initial_master_nodes' is not identified in node bootstrap check #2779
Fix issue that deprecated setting 'cluster.initial_master_nodes' is not identified in node bootstrap check #2779
Conversation
…ot identified during node bootstrap Signed-off-by: Tianli Feng <[email protected]>
Signed-off-by: Tianli Feng <[email protected]>
1a54ea3
to
7c49ddf
Compare
❌ Gradle Check failure 1a54ea37f3d9a2ac2130c134fb1398628efc41b3 |
…ing-node-bootstrap Signed-off-by: Tianli Feng <[email protected]>
In log 4226:
In log 4229:
Opened new issue #2782 to track. |
start gradle check |
In log 4234:
start gradle check |
start gradle check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this fix, @tlfeng can you find other reviews to help merge this blocking change promptly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good enough for now, but I worry that this "setting exists?" may not work correctly in a distributed scenario. Thus this whole business of "what's the name of the actual setting, the new INITIAL_CLUSTER_MANAGER_NODES_SETTING
vs. the deprecated INITIAL_MASTER_NODES_SETTING
should be implemented as a method on Setting itself, e.g. setting.getActualNameOfSettingInConfigurationOrSomethingLikeThat()
, and return the name of the setting used as fallback in the case that it has a fallback, and its own name otherwise. Possible?
…ot identified in node bootstrap check (#2779) * Fix issue that deprecated setting 'cluster.initial_master_nodes' is not identified during node bootstrap Signed-off-by: Tianli Feng <[email protected]> * Restore a variable name Signed-off-by: Tianli Feng <[email protected]> (cherry picked from commit dd24e17)
…ot identified in node bootstrap check (#2779) * Fix issue that deprecated setting 'cluster.initial_master_nodes' is not identified during node bootstrap Signed-off-by: Tianli Feng <[email protected]> * Restore a variable name Signed-off-by: Tianli Feng <[email protected]> (cherry picked from commit dd24e17)
Previously the setting was `cluster.initial_master_nodes` and has since changed to `cluster.initial_cluster_manager_nodes`. This was causing issues due to a bug in the fallback method that has been fixed in OpenSearch, but getting ahead of this change before its needed. See related opensearch-project/OpenSearch#2779 Signed-off-by: Peter Nied <[email protected]>
Previously the setting was `cluster.initial_master_nodes` and has since changed to `cluster.initial_cluster_manager_nodes`. This was causing issues due to a bug in the fallback method that has been fixed in OpenSearch, but getting ahead of this change before its needed. See related opensearch-project/OpenSearch#2779 Signed-off-by: Peter Nied <[email protected]>
…ot identified in node bootstrap check (#2779) (#2794) * Fix issue that deprecated setting 'cluster.initial_master_nodes' is not identified during node bootstrap Signed-off-by: Tianli Feng <[email protected]> * Restore a variable name Signed-off-by: Tianli Feng <[email protected]> (cherry picked from commit dd24e17) Co-authored-by: Tianli Feng <[email protected]>
…ot identified in node bootstrap check (#2779) (#2793) * Fix issue that deprecated setting 'cluster.initial_master_nodes' is not identified during node bootstrap Signed-off-by: Tianli Feng <[email protected]> * Restore a variable name Signed-off-by: Tianli Feng <[email protected]> (cherry picked from commit dd24e17) Co-authored-by: Tianli Feng <[email protected]>
Hi @dblock Thanks for your suggestion! I will take it into account, and will discuss with the team to find a solution to prevent such issue happens in other recent deprecated settings. |
To be clear, I am suggesting the following: current
new
|
Previously the setting was `cluster.initial_master_nodes` and has since changed to `cluster.initial_cluster_manager_nodes`. This was causing issues due to a bug in the fallback method that has been fixed in OpenSearch, but getting ahead of this change before its needed. See related opensearch-project/OpenSearch#2779 Signed-off-by: Peter Nied <[email protected]>
Previously the setting was `cluster.initial_master_nodes` and has since changed to `cluster.initial_cluster_manager_nodes`. This was causing issues due to a bug in the fallback method that has been fixed in OpenSearch, but getting ahead of this change before its needed. See related opensearch-project/OpenSearch#2779 Signed-off-by: Peter Nied <[email protected]>
…ect#1746) Previously the setting was `cluster.initial_master_nodes` and has since changed to `cluster.initial_cluster_manager_nodes`. This was causing issues due to a bug in the fallback method that has been fixed in OpenSearch, but getting ahead of this change before its needed. See related opensearch-project/OpenSearch#2779 Signed-off-by: Peter Nied <[email protected]>
Description
Problem:
The deprecated setting
cluster.initial_master_nodes
is not identified in the node bootstrap check.Although the setting is configured in
opensearch.yml
, the node bootstrap check still fails with messagethe default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_cluster_manager_nodes / cluster.initial_master_nodes] must be configured
.Change:
INITIAL_MASTER_NODES_SETTING
back to accepted discovery settings indiscoveryIsConfigured()
, which used in node bootstrap check.cluster.initial_master_nodes
to test it's an accepted discovery setting.Reason:
The PR #2463 deprecated the setting
cluster.initial_master_nodes
, and added alternative settingcluster.initial_cluster_manager_nodes
.The bug is caused by the the setting
INITIAL_MASTER_NODES_SETTING
was replaced byINITIAL_CLUSTER_MANAGER_NODES_SETTING
directly in the code, while they should both exist. The methoddiscoveryIsConfigured()
is used in this place.Background:
Bootstrapping a cluster is required when an OpenSearch cluster starts up for the very first time. In development mode (single node without joining a cluster), with no discovery settings configured, this is automatically performed by the nodes themselves.
Issues Resolved
Resolve #2769
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.