Operational Defect Database
BugZero found this defect 72 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2603687
Kill for step up should use ErrorCodes::InterruptedDueToReplStateChange
Last update date:
3/12/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
8.0.0-rc0
Description:
Info
We kill all retryable write sessions and invalidate them during step-up. There usually won't be any active ones, but there are some edge cases (e.g. just checked out the session but hadn't taken the global lock at stepdown time) which result in some. This kill is done with the default ErrorCodes::Interrupted; it should be done with ErrorCodes::InterruptedDueToReplStateChange
Top User Comments
xgen-internal-githook commented on Tue, 12 Mar 2024 16:23:29 +0000: Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'} Message: SERVER-87738 Kill for step up should use ErrorCodes::InterruptedDueToReplStateChange GitOrigin-RevId: 276a8829b2550cc6f0cddf8194f185525b303b0b Branch: master https://github.com/mongodb/mongo/commit/77d1199aed797694b1ea8eb50e09453ba5df229b
Steps to Reproduce
