[SERVER-55044] Timestamped reads ahead of all_durable in read_majority_reads.js Created: 08/Mar/21 Updated: 29/Oct/23 Resolved: 22/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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 | ||||
| Sprint: | Repl 2021-03-22, Repl 2021-04-05 | ||||
| Participants: | |||||
| Linked BF Score: | 9 | ||||
| Description |
|
This was because the test manually sets the committed snapshot which may not synchronize well with the actual timestamps managed by the server, especially those internal writes done by the server at startup. We should wait for a valid committed snapshot once before starting the test. |
| Comments |
| Comment by Githook User [ 22/Mar/21 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |