[SERVER-41032] TransactionRouter's _isRecoveringCommit field is not reset on receiving a higher transaction number Created: 07/May/19 Updated: 29/Oct/23 Resolved: 15/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2019-05-20 |
| Participants: |
| Description |
|
I just noticed the _isRecoveringCommit field is set to true here, and checked here, but it's never reset to false. |
| Comments |
| Comment by Githook User [ 15/May/19 ] |
|
Author: {'name': 'Matthew Saltz', 'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com'}Message: |