
OPERATIONAL DEFECT DATABASE
...

...
The FutureResolution mutex is marked level 0. So is the SessionCatalog mutex. This is a problem because while the SessionCatalog mutex is held, we call OperationContext::markKilled, which then resolves a future which requires acquiring the FutureResolution mutex. This is only a problem in tests since there's no actual risk for deadlock - it's just reported as a level violation by the latch analyzer. To fix it we need to either make the SessionCatalog mutex level 1, or make the FutureResolution into a std::mutex with no leveling since it's such a low level component. Acceptance criteria: Remove the hierarchy number from the FutureResolution mutex
xgen-internal-githook commented on Sun, 16 May 2021 15:30:34 +0000: Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'} Message: SERVER-53661 re-enable disable index_commit_currentop_slow.js This reverts commit beb176da79f83da393da9416b3552d00f4ff50c9. Branch: master https://github.com/mongodb/mongo/commit/f856bd9d8ea972ffa55e4762b8164fa2145e8bdb xgen-internal-githook commented on Sun, 16 May 2021 10:23:31 +0000: Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'} Message: SERVER-53661 fix latch name in index_commit_currentop_slow.js Branch: master https://github.com/mongodb/mongo/commit/ca69b62fe50e03922c96a75de509f3ad33fb4363 xgen-internal-githook commented on Sat, 15 May 2021 14:06:15 +0000: Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'} Message: SERVER-53661 temporarily disable index_commit_currentop_slow.js Branch: master https://github.com/mongodb/mongo/commit/beb176da79f83da393da9416b3552d00f4ff50c9 xgen-internal-githook commented on Fri, 14 May 2021 19:50:15 +0000: Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'} Message: SERVER-53661 SessionCatalog mutex is level 0 and is held while acquiring the FutureResolution mutex Branch: master https://github.com/mongodb/mongo/commit/4099baf59544e56922641fe10b5cc07d5a99e591
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.