-
Type:
Bug
-
Resolution: Done
-
Priority:
Critical - P2
-
Affects Version/s: 2.4.14, 2.6.9, 3.0.2, 3.1.2
-
Component/s: Replication, Storage
-
Fully Compatible
-
ALL
-
Run the attached rollback-repro.sh
script (which uses 'mlaunch' to start and manage a 3 node PSA replica set).It runs through a test which forces a rollback but when using MongoDB 3.0.x or 3.1.x the 'rsBackgroundSync' fails to find the data and write it to disk.
Earlier versions of MongoDB, e.g. 2.6.9, correctly handle this case.
Run the attached rollback-repro.sh script (which uses 'mlaunch' to start and manage a 3 node PSA replica set). It runs through a test which forces a rollback but when using MongoDB 3.0.x or 3.1.x the ' rsBackgroundSync ' fails to find the data and write it to disk. Earlier versions of MongoDB, e.g. 2.6.9, correctly handle this case. -
RPL 3 05/15/15
If MongoDB rolls back an explicit collection creation, it will not record the dropped data to disk.
This issue was made more acute in MongoDB 3.0, when all implicit collection creation was changed to explicitly create an oplog entry. Thus, downstream replicating nodes now create all collections explicitly.
- is duplicated by
-
SERVER-20597 Save data that is rolled back to the rollback directory
-
- Closed
-