[DOCS-13722] Investigate changes in SERVER-48083: Support rolling back a collMod oplog entry that modifies an index when using rollback via refetch Created: 22/Jun/20  Updated: 30/Oct/23  Resolved: 08/Jul/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Mihai Andrei Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: docs-indexes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-48083 Support rolling back a collMod oplog ... Closed
Participants:
Days since reply: 3 years, 31 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

In SERVER-48083, we decided not to add support for rolling back a collMod entry that modifies an index's hidden field when using rollback via refetch because rollback via refetch is only used when enableMajorityReadConcern is set to false. Not only is it unlikely that users will run into this in practice since modifying an index via collMod is an uncommon operation, but also support for enableMajorityReadConcern=false may be removed in 4.6. That said, the documentation for enableMajorityReadConcern=false should be updated to reflect that collMod entries which modify an index cannot be be rolled back and any affected nodes will require a full resync.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 08/Jul/20 ]

Author:

{'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}

Message: (DOCS-13722): collMod entries which modify an index cannot be be rolled back
Branch: master
https://github.com/mongodb/docs/commit/4cba7555ad8c807ee020858cbe7e23ee420d2d81

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