Skip to content
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.

use a single global lock to prevent concurrent calls to flush #271

Merged
merged 1 commit into from
Feb 21, 2017
Merged

use a single global lock to prevent concurrent calls to flush #271

merged 1 commit into from
Feb 21, 2017

Conversation

jipperinbham
Copy link
Contributor

more fined grained locking is likely possible but this guarantees flush is not called for the same collection

fixes #269

@jipperinbham
use a single global lock to prevent concurrent calls to flush
0ea445e 
more fined grained locking is likely possible but this guarantees flush is not called for the same collection

fixes #269
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 59.4% when pulling 0ea445e on 269-bulk-lock into fad12d5 on master.

@jipperinbham jipperinbham merged commit f80487c into master Feb 21, 2017
@jipperinbham jipperinbham deleted the 269-bulk-lock branch February 21, 2017 15:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@trinchan trinchan Awaiting requested review from trinchan

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

mongodb bulk calls flush concurrently
2 participants
@jipperinbham @coveralls