[SERVER-12289] When cloning capped collection during initial sync cap the number of cloned objects to size of collection Created: 08/Jan/14 Updated: 06/Dec/22 Resolved: 20/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.8, 2.5.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
Currently if initial sync starts cloning a capped collection that's being written to at a comparable rate to sync rate, it's possible for the sync to go on far longer than it should, and in some cases its cursor can get invalidated by newer inserts which are triggering 'deleteRecord' from 'cappedAlloc' which on capped collection are invalidating the cursor. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 20/Sep/18 ] |
|
We won't be working on this unless there's further user pain. |