[DOCS-9537] Docs for SERVER-23476: Re-enable resync command for replica set nodes Created: 05/Dec/16 Updated: 09/Feb/18 Resolved: 20/Dec/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | bite-sized | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 6 years, 8 weeks, 1 day ago | ||||||||||||
| Description |
|
Engineering Ticket Description: Since we have temporarily disabled the resync command while reworking code and bringing the DataReplicator into the mix, we need to re-enable support for it and its tests. These are the expected behaviors:
|
| Comments |
| Comment by Githook User [ 20/Dec/17 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 20/Dec/17 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Danny Hatcher (Inactive) [ 21/Aug/17 ] |
|
As Kiril said, this is an easy documentation change to make. |
| Comment by Kiril Piskunov [ 27/Jun/17 ] |
|
emily.hall@mongodb.com - we should just mention that change to sync source will restart in-progress initial sync from the new source. |
| Comment by Emily Hall [ 06/Jun/17 ] |
|
kiril.piskunov - this is part of our active backlog, however, it would be great if you could help with some additional details to help me to prioritize against other work. |
| Comment by Kiril Piskunov [ 05/Jun/17 ] |
|
Is there any plans to fix this in the documentation? Our 3.4 docs still state that initial sync will not restart from the new source. https://docs.mongodb.com/manual/reference/command/replSetSyncFrom/#sync-logic |