forked from Tokutek/tokumxse
-
Notifications
You must be signed in to change notification settings - Fork 61
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
FCBIS v7.0 #1345
Draft
igorsol
wants to merge
26
commits into
v7.0
Choose a base branch
from
fcbis-70
base: v7.0
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
FCBIS v7.0 #1345
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
…CursorExtend When something is called by internal client read concern must be explicitly specified.
also split out 'initial_syncer_fcb' library
reconstruct prepared transactions happens in _tearDown_inlock
Fix of the "Fatal message" happened in OplogCapMaintainerThread. Both switch to dummy location and back to dbpath location should be under single global lock.
The thread calling getInitialSyncProgress keeps opCtx and locks trying to acquire initial syncer's mutex. This leaded to deadlock due to fact that storage changing thread waited for destruction of opCtx while keeping initial syncer's mutex
Initial syncer's shutdown() function is called twice: first time when shutdown thread has not created opCtx yet. This allows us to wait for the end of storage change operation and to ensure that no storage change will be running whne shutdown() is called second time (with non-NOOP opCtx already created). This is done to avoid deadlock between shutdown thread and storage change.
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.