[SERVER-41161] Re-enable renaming between databases for applyOps Created: 15/May/19  Updated: 29/Oct/23  Resolved: 21/May/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.12

Type: Task Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-40995 Server latest crashes applying pre 3.... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-06-03
Participants:

 Description   

SERVER-33631 disallowed across database rename for applyOps. But as we need to support mongo mirroring from as old as server version 2.6 to 4.2, oplog entry that renames across database is still possible.



 Comments   
Comment by Githook User [ 21/May/19 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-41161 Re-enable renaming between databases for applyOps
Branch: master
https://github.com/mongodb/mongo/commit/d9d57c2edef4cf974ccf6a527d9cce28baa03079

Comment by Xiangyu Yao (Inactive) [ 20/May/19 ]

I think it's easier to re-enable this feature.

Comment by Eric Milkie [ 16/May/19 ]

How much work is this, compared to changing mongomirror to reinterpret these oplog entries?

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