[SERVER-44844] Document the use of archived data files Created: 26/Nov/19 Updated: 02/Jan/20 Resolved: 30/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Raiden Worley (Inactive) | Assignee: | Raiden Worley (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | STM 2019-12-26, STM 2020-01-09 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Now that data files can be consistently used to resurrect mongod instances, investigate more thoroughly how these instances behave and document these behaviors and how they can be used. |
| Comments |
| Comment by Raiden Worley (Inactive) [ 30/Dec/19 ] |
|
Published wiki page: https://github.com/mongodb/mongo/wiki/Archived-Data-Files |
| Comment by Raiden Worley (Inactive) [ 26/Dec/19 ] |
|
Not sure if people other than me can see the wiki article draft, let me know if not: https://wiki.corp.mongodb.com/pages/resumedraft.action?draftId=100254632&draftShareId=691e5079-3791-4cbf-bb66-cfb98faaf8ef Didn't find anything too odd other than the whole thing where nodes enter the REMOVED state easily. So I mostly wrote the article as a reference for server ppl with some recommendations. |
| Comment by Robert Guo (Inactive) [ 26/Nov/19 ] |
|
Try spinning up a replset and a sharded cluster from the data files and document any unintuitive behavior. |