workload/tpcc: add next-order-id repairing option for LDR support #135265
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The 'next order id' field of district has a sequence-like behavior that is not a good fit for async replication by LDR, but we can adapt the workload to at least repair the sequence so that it self-heals after a conflict and can at least continue to accept future orders rather than . bringing all traffic to a halt.
Release note: none.
Epic: none.