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

Container consistency policy #300

Closed
roman-khimov opened this issue Jun 27, 2024 · 1 comment · Fixed by #309
Closed

Container consistency policy #300

roman-khimov opened this issue Jun 27, 2024 · 1 comment · Fixed by #309
Labels
feature Completely new functionality I2 Regular impact S2 Regular significance U2 Seriously planned
Milestone

Comments

@roman-khimov
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when we can't specify consistency policy for a container.

Describe the solution you'd like

Add an optional enum field with the following options:

  • available (just like the old one, no meta)
  • strict (nodes use meta and wait for meta acceptance)
  • optimistic (nodes use meta, but do not wait for acceptance)

Describe alternatives you've considered

If we want to alternate between different modes and preserve compatibility, there are not a lot of them.

@roman-khimov roman-khimov added U2 Seriously planned S2 Regular significance I2 Regular impact feature Completely new functionality labels Jun 27, 2024
@roman-khimov
Copy link
Member Author

CC @EESergey. This can be an attribute.

carpawell added a commit that referenced this issue Oct 16, 2024
carpawell added a commit that referenced this issue Oct 17, 2024
carpawell added a commit that referenced this issue Oct 17, 2024
@roman-khimov roman-khimov added this to the v2.17.0 milestone Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Completely new functionality I2 Regular impact S2 Regular significance U2 Seriously planned
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant