Server should not start if datafiles from other storage engine are present in dbpath

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.8.0-rc0
    • Component/s: Storage, Usability
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Say I start mongod with mmapv1 enabled in a clean directory:

      mongod --dbpath=mongodata --storageEngine=mmapv1
      

      Then exit the server.

      then if I start the server with the same dbpath but with wiredtiger:

      mongod --dbpath=mongodata --storageEngine=wiredtiger
      

      the server will happily start writing data files to the same directory mmapv1 was using. (Also happens if I do wiredtiger, than mmap)

      This is probably going to cause some confusion and/or misconfiguration at some point. I think it would be better if we detected that we are starting in a non-empty dbpath with incompatible data files and refuse to start.

            Assignee:
            Unassigned
            Reporter:
            Adam Midvidy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: