-
Notifications
You must be signed in to change notification settings - Fork 104
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
Timeout setting file lock #2988
Draft
ScottDugas
wants to merge
9
commits into
FoundationDB:main
Choose a base branch
from
ScottDugas:timeout-setting-file-lock
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Timeout setting file lock #2988
ScottDugas
wants to merge
9
commits into
FoundationDB:main
from
ScottDugas:timeout-setting-file-lock
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Setting up the executor as a ForkJoinPool and trying to do concurrent updates can cause a deadlock.
The only implementation that actually referenced the text was in tests. Those tests need to be adjusted, but this makes it so that the type aligns with the behavior, and hopefully gets us on a path to an index having a fixed analyzer (at least for the lifetime of the transaction), which can simplify the FDBDirectoryWrapper
Result of fdb-record-layer-pr on Linux CentOS 7
|
Since there is no longer a text parameter, it can generater the wrappers once. This may result in some wasted CPU generating unused analyzers (e.g. when not querying or not writing), but it should be compensated by the fact that it consistently creates 2 wrappers, rather than creating a wrapper for every record update, or every query.
Only initialize this once, and reuse. Part of the process of making FDBDirectoryWrapper not have to worry about changing analyzers
Since the analyzer is passed into the constructor, there's no reason for the writer to change.
By using a LazyCloseable instead of synchronized blocks, it allows the ForkJoinPool to mark the thread as inactive, and will create new threads to process operations, thus avoiding the deadlock
I had to disable: - synthetic indexes, because updating the parent and child at the same time breaks the primaryKeySegmentIndex - partitioning because the partitionInfo (including counts) is not updated in a thread-safe way
Result of fdb-record-layer-pr on Linux CentOS 7
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.