[SERVER-57139] Correctly wait for rollback to complete in rollback_with_coalesced_txn_table_updates_during_oplog_application.js Created: 21/May/21 Updated: 29/Oct/23 Resolved: 24/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Wenbin Zhu | Assignee: | Wenbin Zhu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Repl 2021-05-31 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 42 | ||||||||
| Description |
|
When crashAfterRollbackTruncation is false, we didn't wait for rollback to begin, so it's possible that when calling awaitNodesAgreeOnPrimary(), secondary1 has not started rollback, but already saw the new primary, and thus awaitNodesAgreeOnPrimary() will not see the network exception, but after this, rollback starts and connection closed, so the replSetFreeze() command sees the network exception. We should wait for rollback to complete before stepping it up. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 25/May/21 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: (cherry picked from commit a5caa6782ad3f2cbe78e66bdeb258931a22ac348) |
| Comment by Githook User [ 24/May/21 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: |