[SERVER-58987] Fix read_only_test.js to avoid start point beyond end point during replication recovery. Created: 30/Jul/21 Updated: 29/Oct/23 Resolved: 04/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.3, 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-08-09 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 28 | ||||||||
| Description |
|
read_only_test.js can hit an the uassert because the start point of the recovery is beyond the end point. The end point is provided by the test, which is the operation time of some previous writes. The start point is the WT recovery_timestamp, which is set to the last checkpoint_timestamp. The problem is when the node was shut down, it took a checkpoint at the stable timestamp, which could be after the operation time that the test recorded before, so when restarting the node, the recovery_timestamp becomes greater than the operation time and caused the failure. |
| 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 [ 06/Aug/21 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: (cherry picked from commit 34d4ebe95b0862b17bf44b4112313ccdbe415289) |
| Comment by Githook User [ 04/Aug/21 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: |