[DOCS-13365] Investigate changes in SERVER-43277: Implement resume after collection drop and rename in CollectionCloner query. Created: 23/Jan/20 Updated: 13/Nov/23 Resolved: 17/Apr/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | docs-replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 42 weeks, 5 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary Initial sync is now resilient to collection drop/rename as well. Resuming the collection clone after rename uses the same machinery as in Description of Linked Ticket Implement resume after collection drop and rename in CollectionCloner query. This should include re-enabling any tests disabled in Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 17/Apr/20 ] |
|
Author: {'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}Message: |