[SERVER-77223] dbcheck_detects_data_corruption.js needs to wait for primary to log healthlog entry Created: 17/May/23 Updated: 31/Oct/23 Resolved: 23/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v7.0, v6.0
|
||||||||
| Sprint: | Execution Team 2023-05-29 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 14 | ||||||||
| Description |
|
The test waits for the secondary to log the "dbCheckStop" entry, but that is not enough to guarantee that the primary has logged its entry. This is because health log entries are written asynchronously with replicating the oplog entries. On slow machines, it could be possible to replicate the dbCheckStop oplog entry and have the secondary write to its healthlog before the primary. |
| Comments |
| Comment by Githook User [ 21/Aug/23 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: (cherry picked from commit 18f5985325621c8fb2666fc3c4f3bf614bbdd6cc) |
| Comment by Uladzimir Makouski [ 05/Jun/23 ] |
|
BFG-1965379 looks like a reoccurrence on v7.0 branch |
| Comment by Githook User [ 22/May/23 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |