Skip to content
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

Add index level setting for remote store #3243

Conversation

sachinpkale
Copy link
Member

@sachinpkale sachinpkale commented May 9, 2022

Signed-off-by: Sachin Kale [email protected]

Description

As explained in V1 of remote store, uploading translog and segments to remote store will be at index level and the setting can be provided while creating the index. This change adds a final index level setting.

Issues Resolved

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff

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.

@eirsep
Copy link
Member

eirsep commented May 9, 2022

What if someone wants remote store setting to be true for all indices by default.

Can the default value be behind a setting too?

@sachinpkale
Copy link
Member Author

What if someone wants remote store setting to be true for all indices by default.

Can the default value be behind a setting too?

In that case, user needs to provide the setting with true value while creating each index. IMO, setting for a setting creates confusion more than the flexibility it provides.

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Check success bb259ec8083377b2fc5a66ce2dfd59d87451bb3a
Log 5146

Reports 5146

Comment on lines +281 to +290
public static final String SETTING_REMOTE_STORE = "index.remote_store";
/**
* Used to specify if the index data should be persisted in the remote store.
*/
public static final Setting<Boolean> INDEX_REMOTE_STORE_SETTING = Setting.boolSetting(
SETTING_REMOTE_STORE,
false,
Property.IndexScope,
Property.Final
);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if we should have separate controls for remote segment store and remote translog store

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, we may need to provide a granular control. Once we finalize these settings, we can either add them or split this one. Let me add it as an issue in the Meta Issue.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or I will keep updating the parent issue of this PR: #3141.

Copy link
Collaborator

@nknize nknize left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's put this behind an opensearch.experimental.feature.remote_store.enabled feature flag that was introduced in #3037

@nknize nknize added feature New feature or request Indexing & Search v3.0.0 Issues and PRs related to version 3.0.0 experimental Marks issues as experimental labels May 9, 2022
@sachinpkale sachinpkale force-pushed the feature/durability-enhancements branch from bb259ec to 8b6bdfa Compare May 10, 2022 04:12
@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Check success 8b6bdfa
Log 5192

Reports 5192

@Bukhtawar Bukhtawar merged commit bcfd328 into opensearch-project:feature/durability-enhancements May 10, 2022
sachinpkale added a commit to sachinpkale/OpenSearch that referenced this pull request May 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
experimental Marks issues as experimental feature New feature or request Indexing & Search v3.0.0 Issues and PRs related to version 3.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants