-
Notifications
You must be signed in to change notification settings - Fork 24.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
Change skip_unavailable default value to true #105792
Merged
quux00
merged 20 commits into
elastic:main
from
quux00:ccs/skip_unavailable-defaults-to-true
Apr 29, 2024
Merged
Changes from 18 commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
0a3516e
Change skip_unavailable default value to true
quux00 05ca1e6
Update docs/changelog/105792.yaml
quux00 1c353c3
Filled in details and impact section of the yaml changelog
quux00 9fbbaf4
Intmd commit - revert me
quux00 8ebd627
Corrected breaking change changelog. Modified security/qa tests to pa…
quux00 2d7d868
Fixed several more tests. Not all passing yet.
quux00 3fb0896
Set my_remote_cluster skip_unavailable to false to let tests pass in …
quux00 7c5c718
Set skip_unavailable=false in qa/multi-cluster-search-security/legacy…
quux00 623b5be
Adjusted more tests to pass
quux00 57c645e
Updated end user API docs around skip_unavailable changes
quux00 154c606
reverted two small unintentional changes
quux00 520ec7b
Changed API docs to specify that the change occurs in 8.15, not 8.14
quux00 7d1692b
Merge remote-tracking branch 'elastic/main' into ccs/skip_unavailable…
quux00 9de832f
Adjusted RemoteClusterSecurityEsqlIT to handle the new skip_unavailab…
quux00 49b1200
Merge remote-tracking branch 'elastic/main' into ccs/skip_unavailable…
quux00 4235b14
Updated RemoteClusterSecurityEsqlIT to test both values of skip_unava…
quux00 16f54ee
Added skip_unavailable=true variants to various tests
quux00 5e27ec5
Fixed failing test in RemoteClusterClientTests
quux00 bc3eea5
Merge remote-tracking branch 'elastic/main' into ccs/skip_unavailable…
quux00 89dbd31
Adding migration info about skip_unavailable to remote-clusters-setti…
quux00 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
pr: 105792 | ||
summary: "Change `skip_unavailable` remote cluster setting default value to true" | ||
area: Search | ||
type: breaking | ||
issues: [] | ||
breaking: | ||
title: "Change `skip_unavailable` remote cluster setting default value to true" | ||
area: Cluster and node setting | ||
details: The default value of the `skip_unavailable` setting is now set to true. | ||
All existing and future remote clusters that do not define this setting will use the new default. | ||
This setting only affects cross-cluster searches using the _search or _async_search API. | ||
impact: Unavailable remote clusters in a cross-cluster search will no longer cause the search to fail unless | ||
skip_unavailable is configured to be `false` in elasticsearch.yml or via the `_cluster/settings` API. | ||
Unavailable clusters with `skip_unavailable`=`true` (either explicitly or by using the new default) are marked | ||
as SKIPPED in the search response metadata section and do not fail the entire search. If users want to ensure that a | ||
search returns a failure when a particular remote cluster is not available, `skip_unavailable` must be now be | ||
set explicitly. | ||
notable: false |
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
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
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
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -87,7 +87,7 @@ public final class RemoteClusterService extends RemoteClusterAware implements Cl | |
public static final Setting.AffixSetting<Boolean> REMOTE_CLUSTER_SKIP_UNAVAILABLE = Setting.affixKeySetting( | ||
"cluster.remote.", | ||
"skip_unavailable", | ||
(ns, key) -> boolSetting(key, false, new RemoteConnectionEnabled<>(ns, key), Setting.Property.Dynamic, Setting.Property.NodeScope) | ||
(ns, key) -> boolSetting(key, true, new RemoteConnectionEnabled<>(ns, key), Setting.Property.Dynamic, Setting.Property.NodeScope) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the only production code change. Everything else is tests and docs. |
||
); | ||
|
||
public static final Setting.AffixSetting<TimeValue> REMOTE_CLUSTER_PING_SCHEDULE = Setting.affixKeySetting( | ||
|
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
Oops, something went wrong.
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.
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.
Maybe obvious, but should we be explicit about the upgrade path: once you upgrade the coordinating node / cluster, where the remotes are registered, you get the new behavior? Say that the coord cluster has multiple nodes that are upgraded one by one (rolling upgrade) what would be the behavior there?
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 point, but that is very specific to a one-time upgrade, so should that go in the "permanent" API docs? Or should it go into some one-time doc like the changelog or deprecation announcement?
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.
Normally we have migration guides for major upgrades and related changes. This is one of those changes but it goes out in a minor, I don't know if we a place for this scenario in the docs.
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.
I added a blurb here about that and we'll also include in the 8.15 release notes. Thanks for flagging this.