[DOCS-15807] [Server]: Stronger warnings for replica set roll back and rollback files Created: 09/Jan/23  Updated: 30/Oct/23  Resolved: 02/Aug/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: Alan Zheng Assignee: Jeffrey Allen
Resolution: Fixed Votes: 3
Labels: proactive
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 27 weeks ago

 Description   

Customers using MongoDB Version 4.4+ AND write concern: 1 should better understand the risk of using write concern:1.

Our current documentation is vague in terms severity of what rollback means. I propose we create warning blocks placed higher in the documentation page for rollback file, specifically to call out that Rollback Files will:  

  • Excludes collection drop or document deletion operations
  • Choosing to restart the primary node in the presence of an oplog hole will result in the exclusion of writes written to the oplog after an oplog hole. MongoDB primary nodes perform writes in parallel, and batch applies oplog entries in parallel. Because these operations are done in parallel, they can cause temporary gaps in the oplog from entries that are not yet written, called oplog holes.


 Comments   
Comment by Sheila Doyle [ 02/Aug/23 ]

jeffrey.allen@mongodb.com lgtm

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