[DOCS-11927] Backup of config server should be updated for CSRS Created: 31/Jul/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | csrsupgrade | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ttps://docs.mongodb.com/manual/tutorial/backup-sharded-cluster-metadata/ |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.3 |
| Description |
|
---------------------------- Original DescriptionDocumentation at https://docs.mongodb.com/manual/tutorial/backup-sharded-cluster-metadata/ states the following:
The above is true for SCCC only. For CSRS, writes to the config server would still occur as long as there's a majority of data bearing nodes available. I suggest two alternatives for CSRS specific documentation, depending on the user requirement:
IMO the second goal can be achieved by either shutting down a majority of nodes, or via fsynlock(). ---------------------------- DescriptionScope of changes (files that need work and how much)Impact to other docs outside of this productMVP (work and date?)Resources (e.g. Scope Docs, Invision) |
| Comments |
| Comment by Education Bot [ 31/Oct/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! |