[DOCS-636] Provide a more detailed discussion of rollback scenarios Created: 23/Oct/12  Updated: 30/Oct/23  Resolved: 14/Nov/12

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-2.2
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Bob Grabar
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-119 Preventing and Handling Rollbacks Closed
Participants:
Days since reply: 11 years, 17 weeks, 1 day ago

 Description   

We give an overview of what rollbacks are, but no examples of where the file would be created and named (we do say it's in the dbpath though). We should probably describe a couple different scenarios of how to deal with the rolled back data. For example, in an insert only app, it would be appropriate to just re-insert the data into the primary. However, in many applications, it is a bad idea to blindly re-insert the data. The user will have to write the data into a temporary collection, then read each document, do some sort of checking and decide whether to re-insert or not. This is highly application dependent, so quite difficult to prescribe exact recipe for how to deal. This point should be made very clear.


Generated at Thu Feb 08 07:39:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.