Skip to content

KV Read-after-Write Consistency #6557

@ripienaar

Description

@ripienaar

Proposed change

Since introducing Direct Get we lost our, admittedly imperfect, read-after-write consistency in KV stores.

We felt then that was an acceptable behaviour change but its clear that there are significant need for control in this area.

We might still default to the current behaviour but should at least provide a opt-in to be in-cluster consistent and in-supercluster eventually consistent.

This can take a few forms:

  • We can add a leader-only direct get subject
  • We can adopt some of the thoughts @MauriceVanVeen has around improving the consistency of the raft layer

Even if we do nothing, we should very clearly and prominently document what we do and do not support in places other than the ADR.

Use case

Increase the areas KV is applicable

Contribution

No response

Metadata

Metadata

Labels

2.12+Features for 2.12 and beyondacceptedThe defect or proposal as been acceptedneeds designNeeds design or ADRneeds infoAdditional info is neededproposalEnhancement idea or proposal

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions