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

Implement retry-based conflict resolution #3397

Open
wjones127 opened this issue Jan 20, 2025 · 0 comments
Open

Implement retry-based conflict resolution #3397

wjones127 opened this issue Jan 20, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@wjones127
Copy link
Contributor

Right now, Transaction::conflicts_with returns a boolean. But if we can differentiate between conflicts that can be retried, and those that can't, then we can have the operations themselves retry. This should be enough to make common operations like append, update, upsert, delete, create_index, and compaction always succeed despite concurrency.

Making this differentiation is also a pre-requisite for #3068, as we'll need to do a similar differentiation for things that can be automatically resolved.

@wjones127 wjones127 added the enhancement New feature or request label Jan 20, 2025
@wjones127 wjones127 self-assigned this Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant