[SERVER-23932] Get collection info ASAP after listDatabases in DataReplicator::InitialSync Created: 26/Apr/16 Updated: 02/Aug/16 Resolved: 02/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Benety Goh |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | DataReplicator, initialSync | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Repl 14 (05/13/16), Repl 15 (06/03/16), Repl 16 (06/24/16), Repl 17 (07/15/16), Repl 18 (08/05/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Since there is a race on cloning collections. applying the oplog, and drop collection/db we should get the collection info for all databases as soon as possible during initial sync. |
| Comments |
| Comment by Benety Goh [ 02/Aug/16 ] |
|
Taking different approach. See |
| Comment by Scott Hernandez (Inactive) [ 25/Jul/16 ] |
|
This already works this way and we just need to verify it stays that way once the cloner scheduler work is done. |