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

allowing multiple storage engines in same dbpath creates opportunity for error

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.8.0-rc0
    • Component/s: None

      Consider a scenario where a customer by mistake starts mongod with the wrong storage engine parameter in a production system. Under the current design mongod will start up and create an empty db in dbpath using that wrong storage engine. Queries to that mongod will begin to fail; it may also begin accepting data and putting it in the wrong db, creating a difficult situation to recover from. We could eliminate this possible source of error by refusing to start if the files currently in dbpath are for a storage engine different from the startup option.

            Assignee:
            Unassigned Unassigned
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: