[SERVER-61409] Investigate the cause of invalidated config.image_collection entries after restart Created: 11/Nov/21 Updated: 31/Mar/22 Resolved: 22/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Jason Chan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | This is the patch containing the jstest (and additional logging) for reproducing these errors. |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
If a replica set that has run findAndModify retryable writes shuts down and then restarts, the secondary from before restart can end up with invalid config.image_collections entries ("invalidatedReason"="minvalid suggests inconsistent snapshot", similar to BF-22250), and if
Here is the link to the EVG patch. |
| Comments |
| Comment by Jason Chan [ 18/Nov/21 ] |
|
cheahuychou.mao do you think this can be resolved? |