Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-18211

MongoDB fails to correctly roll back collection creation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: 2.4.14, 2.6.9, 3.0.2, 3.1.2
    • Fix Version/s: 2.6.10, 3.0.3, 3.1.3
    • Component/s: Replication, Storage
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Steps To Reproduce:
      Hide

      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.

      Show
      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.
    • Sprint:
      RPL 3 05/15/15

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: