-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
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.)
- depends on
-
SERVER-48083 Support rolling back a collMod oplog entry that modifies an index when using rollback via refetch
- Closed