Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Remove support for internal versioning for concurrency control #38254
Elasticsearch has long supported compare and set (a.k.a optimistic concurrency control) operations using internal document versioning. Sadly that approach is flawed and can sometime do the wrong thing. Here's the relevant excerpt from the resiliency status page:
We recently introduced a new sequence number based approach that doesn't suffer from this dirty reads problem.
This PR removes support for internal versioning as a concurrency control mechanism in favor of the sequence number approach.
Relates to #1078