Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
Backlog
-
None
-
Fully Compatible
-
Repl 2017-08-21, Repl 2017-09-11
-
0
Description
Currently, when we rename across databases, a problem arises with rollback when we are trying to refetch a document in a collection that has been renamed across databases. Even if we are querying by UUID's, because the collection has been copied into another database, this action makes the UUID of the collection to change. Thus, although the document does exist, just under a different namespace and UUID, we will not be able to refetch it during rollback. This leads to data corruption between the sync source and rolling back node.
A fix for this would be to make the oplog entry for renameCollection a set of create, insert and delete oplog entries instead of a singular oplog entry. This means that even if during rollback, we cannot refetch the document by UUID, when the node has transitioned out of roll back state and into secondary state, we can apply the insertions and maintain consistency.
Attachments
Issue Links
- depends on
-
SERVER-30900 remove collMod writeConcern argument from ReplSetTest.checkReplicaSet()
-
- Closed
-
-
-
- Closed
-
- is depended on by
-
-
- Backlog
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-
-
SERVER-39587 Include the final collection name in each oplog entry for commands using temporary collections
-
- Closed
-