[SERVER-25114] Create collection cloner scheduler Created: 15/Jul/16 Updated: 06/Dec/22 Resolved: 29/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | 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
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 18 (08/05/16) | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Create a scheduler to use when doing initial sync which is passed into the DatabaseCloner and is responsible for the order, concurrency and retry behavior during initial sync. The scheduler should live above the DatabaseCloner so that it make decision across databases. It will be responsible for starting the actual CollectionCloners. SERVER-24793 will create a new scheduler which knows how to restart failed CollectionCloners. |
| Comments |
| Comment by Benety Goh [ 01/Aug/16 ] |
|
Taking a different approach - see |
| Comment by Githook User [ 27/Jul/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 26/Jul/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: Revert " This reverts commit e9b0b39bbf6a277ab470f7f7ee5bb313d5f1f434. |
| Comment by Githook User [ 26/Jul/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 20/Jul/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |