Race fix: Acquire lock in fetchAndLoadDatabase before calling _fetchAndLoadDatabase #6638
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.
This race appears to have cropped up now we're running more tests with Rosmar.
fetchAndLoadDatabase
wasn't acquiring the lock before falling into_fetchAndLoadDatabase
which seems obviously wrong. I've scanned usages of both methods and the locking seems correct based on_
prefix usage (i.e. we're not going to be accidentally double locking)Integration Tests
GSI=true,xattrs=true
https://jenkins.sgwdev.com/job/SyncGateway-Integration/2254/