[DOCS-11568] User should not run renameCollection during initial sync phase of mongomirror and live migration even for MongoDB v3.6 Created: 10/Apr/18 Updated: 21/Jun/18 Resolved: 21/Jun/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nishant Bhardwaj | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 33 weeks, 6 days ago |
| Story Points: | 0.2 |
| Description |
|
MongoDB Atlas live migrate docs and mongomirror docs should mention the limitation related to renameCollection. While MongoDB v3.6 supports renameCollection during initial sync for its replica set members, the tools/drivers do not currently have this capability. So to avoid confusion the renameCollection limitation should be mentioned in live migrate and mongomirror pages of MongoDB Atlas documentation. |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 21/Jun/18 ] |
|
merged and published |