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

LucenePartitioner is not thread safe if multiple independent records are updated concurrently #2990

Open
ScottDugas opened this issue Dec 4, 2024 · 0 comments
Assignees

Comments

@ScottDugas
Copy link
Contributor

If multiple different records in the same partition are added concurrently the counts can get skewed, and in theory, so can the endpoints, although that's less likely.

@ScottDugas ScottDugas self-assigned this Dec 4, 2024
ScottDugas added a commit to ScottDugas/fdb-record-layer that referenced this issue Dec 9, 2024
This changes the concurrentUpdate to run with a single partition,
and adds usages of AsyncLock to ensure that updates to the partition
metadata work correctly.
Before calling the issue complete an additional test should be added
that does concurrent inserts, and one for concurrent deletes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant