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

FCBIS v7.0 #1345

Draft
wants to merge 26 commits into
base: v7.0
Choose a base branch
from
Draft

FCBIS v7.0 #1345

wants to merge 26 commits into from

Conversation

igorsol
Copy link

@igorsol igorsol commented Nov 15, 2024

No description provided.

igorsol added 26 commits May 29, 2024 19:54
…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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant