[DOCS-4793] Documented procedure for downtime-minimised separation of a database onto another replica set Created: 09/Feb/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Story Points: | 3.5 | ||||
| Description |
|
Sometimes it becomes apparent that a set of databases on a cluster/replica set need to be moved onto their own, separate cluster/replica set (eg. they have distinctly different usage patterns to the rest of the databases, or are otherwise impacting performance). It would be good to have documentation that describes the possible approaches to doing this, and for each alternative, the difficulty/complexity and downtime requirements. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |