TDBStore: Unlock the master mutex even after garbage_collect() #11971
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.
Description
Summary of change
TDBStore::set() was leaving a mutex locked in case it failed to write a data, and then started a garbage collection phase.
Fixed the sequence so that mutex is always unlocked, regardless of whether we run the GC or not.
Fixes #11723
Pull request type
Test results
Reviewers
@VeijoPesonen