[SERVER-53844] Ensure insert into new collection is replicated before asserting in initial_sync_drop_against_last_stable.js Created: 15/Jan/21 Updated: 29/Oct/23 Resolved: 22/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.3 |
| Fix Version/s: | 4.4.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Jason Chan |
| 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-01-25 | ||||
| Participants: | |||||
| Linked BF Score: | 16 | ||||
| Description |
|
Currently, as part of initial_sync_drop_against_last_stable.js, we drop a collection and then create a new one with the same name. We also insert a document into the new collection and check that it exists once initial sync is complete. Currently, there is a race that the document is not covered by initial sync (the optime for the insert is > than the stopOptime for initial sync), and we fail the assertion that the inserted document exists after initial sync is complete. |
| Comments |
| Comment by Githook User [ 22/Jan/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |