-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Update validator for index.routing.allocation.total_primary_shards_per_node
for index update requests.
#17474
base: main
Are you sure you want to change the base?
Update validator for index.routing.allocation.total_primary_shards_per_node
for index update requests.
#17474
Conversation
… index per node. Added relevant files for unit test and integration test. Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
…MENT replication indices Signed-off-by: Divyansh Pandey <[email protected]>
…mary shards per node settings only for remote store enabled cluster. Added relevant unit and integration tests. Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
Signed-off-by: Divyansh Pandey <[email protected]>
…chFork Merge main to sync changelog updates with local changes.
…et for cluster which is not remote store enabled Signed-off-by: Divyansh Pandey <[email protected]>
…d relevant integration tests Signed-off-by: Divyansh Pandey <[email protected]>
} | ||
|
||
// Check if remote store is enabled | ||
boolean isRemoteStoreEnabled = clusterService.state() |
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.
Not ideal, but I see why we needed to do this. Since index settings update is an infrequently invoked API, I think we can keep this here.
@sachinpkale I couldn't see a better way to check if remote store is enabled in this code block. Do you see a better way to do this here?
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.
Do we know how this is handled in MetadataCreateIndexService
?
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #17474 +/- ##
============================================
+ Coverage 72.42% 72.44% +0.02%
- Complexity 65611 65632 +21
============================================
Files 5304 5304
Lines 304743 304756 +13
Branches 44189 44191 +2
============================================
+ Hits 220701 220792 +91
+ Misses 65888 65865 -23
+ Partials 18154 18099 -55 ☔ View full report in Codecov by Sentry. |
Description
When attempting to update the index.routing.allocation.total_primary_shards_per_node setting for an existing index in a remote store enabled cluster, an error is encountered stating that this setting can only be used with remote store enabled clusters, despite the cluster actually being remote store enabled.
Changes in this PR, updates the validator for update index setting. The change aims to resolve bug identified in #17295
Related Issues
Resolves #17473
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.