[SERVER-48285] Remove lastCommitted checks in no_progress_updates_during_initial_sync.js Created: 19/May/20 Updated: 29/Oct/23 Resolved: 21/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc9, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Vesselina Ratcheva (Inactive) |
| 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: |
v4.4
|
||||||||
| Sprint: | Repl 2020-06-01 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 9 | ||||||||
| Description |
|
It is actually valid for the lastOpCommitted to advance on the initial syncing node, as tested in |
| Comments |
| Comment by Githook User [ 21/May/20 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |