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

[Segment Replication + Remote Storage] Remove implicit replication strategy change when configuring remote storage. #8162

Closed
mch2 opened this issue Jun 20, 2023 · 0 comments · Fixed by #8186 or #8235
Assignees
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request

Comments

@mch2
Copy link
Member

mch2 commented Jun 20, 2023

Is your feature request related to a problem? Please describe.
Today when enabling remote storage for an index segrep will be enabled behind the scenes. This is misleading as user is not expecting to change replication strategy when configuring remote storage. There is a current limitation that remote storage is not supported with docrep, but could be in the future and would require reverting this coupling.

Describe the solution you'd like
Require replication strategy to explicitly be set as segment (either via cluster setting or in req) for remote storage to be enabled. Throw an exception if docrep is on the index.

Describe alternatives you've considered
Leave as is.

Additional context
None

@mch2 mch2 added enhancement Enhancement or improvement to existing feature or request untriaged labels Jun 20, 2023
@mch2 mch2 changed the title [Segment Replication + Remote Storage] Require segment replication setting when configuring remote storage. [Segment Replication + Remote Storage] Remove implicit replication strategy change when configuring remote storage. Jun 20, 2023
@anasalkouz anasalkouz moved this from Todo to In Progress in Segment Replication Jun 22, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Segment Replication Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment