-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Rename static Zen1 settings #38333
Rename static Zen1 settings #38333
Conversation
Renames the following settings to remove the mention of `zen` in their names: - `discovery.zen.hosts_provider` -> `discovery.seed_providers` - `discovery.zen.ping.unicast.concurrent_connects` -> `discovery.seed_resolver.max_concurrent_resolvers` - `discovery.zen.ping.unicast.hosts.resolve_timeout` -> `discovery.seed_resolver.timeout` - `discovery.zen.ping.unicast.hosts` -> `discovery.seed_addresses`
Pinging @elastic/es-distributed |
@elasticmachine run elasticsearch-ci/1 |
+ | ||
Defaults to `["127.0.0.1", "[::1]"]`. | ||
existent IP addresses will throw exceptions and cause another DNS lookup on the | ||
next round of pinging (subject to JVM DNS caching). + Defaults to |
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.
there is a + here
} | ||
}); | ||
BiConsumer<DiscoveryNode, ClusterState> joinValidator = plugin.getJoinValidator(); | ||
if (joinValidator != null) { | ||
joinValidators.add(joinValidator); | ||
} | ||
} | ||
List<String> hostsProviderNames = DISCOVERY_HOSTS_PROVIDER_SETTING.get(settings); | ||
|
||
List<String> hostsProviderNames = getSeedProviderNames(settings); |
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.
rename this variable as well?
@@ -41,8 +41,6 @@ | |||
import java.util.concurrent.atomic.AtomicBoolean; | |||
import java.util.function.Consumer; | |||
|
|||
import static org.elasticsearch.discovery.zen.UnicastZenPing.DISCOVERY_ZEN_PING_UNICAST_CONCURRENT_CONNECTS_SETTING; | |||
|
|||
public class UnicastConfiguredHostsResolver extends AbstractLifecycleComponent implements ConfiguredHostsResolver { |
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.
we can rename these classes in a follow-up
Setting.positiveTimeSetting("discovery.zen.ping.unicast.hosts.resolve_timeout", TimeValue.timeValueSeconds(5), | ||
Property.NodeScope, Property.Deprecated); | ||
|
||
public static final Setting<Integer> DISCOVERY_SEED_RESOLVER_MAX_CONCURRENT_RESOLVERS_SETTING = |
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.
a bit ugly that we have to define this new setting in this class that's going away. We can clean that up later though when removing Zen1
* master: Mute failing API key integration test (elastic#38409) Change the milliseconds precision to 3 digits for intervals. (elastic#38297) SecuritySettingsSource license.self_generated: trial (elastic#38233) Rename no-master-block setting (elastic#38350) Rename static Zen1 settings (elastic#38333) Migration doc for audit json log file (elastic#38165) Add apm_user reserved role (elastic#38206)
In elastic#38333 and elastic#38350 we moved away from the `discovery.zen` settings namespace since these settings have an effect even though Zen Discovery itself is being phased out. This change aligns the documentation and the names of related classes and methods with the newly-introduced naming conventions.
Zen discovery and its associated settings were deprecated in 7.0. This commit adds an entry to the release notes calling this out. Relates elastic#38289 elastic#38333 elastic#38350 elastic#37868
Renames the following settings to remove the mention of
zen
in their names:discovery.zen.hosts_provider
->discovery.seed_providers
discovery.zen.ping.unicast.concurrent_connects
->discovery.seed_resolver.max_concurrent_resolvers
discovery.zen.ping.unicast.hosts.resolve_timeout
->discovery.seed_resolver.timeout
discovery.zen.ping.unicast.hosts
->discovery.seed_hosts
The old names are still supported, but deprecated, and we reject attempts to
use both old and new names at the same time.