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

system.profile in non-local dbs will trigger a 3.4 downgrade prior to rs initiate

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Storage Execution
    • ALL
    • Hide

      1. Start mongod
      ./mongod --replSet foo --bind_ip 0.0.0.0
      2. Start mongo
      ./mongo
      3. Create test.system.profile
      db.setProfilingLevel(2)
      4. Shut down mongod
      use admin
      db.shutdownServer()
      5. Restart mongod
      The log shows this message and aborts startup: 

      ** IMPORTANT: There is no feature compatibility document. A 3.4 binary must be used.
**
      Show
      1. Start mongod ./mongod --replSet foo --bind_ip 0.0.0.0 2. Start mongo ./mongo 3. Create test.system.profile db.setProfilingLevel(2) 4. Shut down mongod use admin db.shutdownServer() 5. Restart mongod The log shows this message and aborts startup: ** IMPORTANT: There is no feature compatibility document. A 3.4 binary must be used. **

      A system.profile collection can be created in any replicated database prior to an initiation of a replica set. mongod startup code currently assumes that if any non-local databases exist, they must have been created with 3.4, but this is not true for system.profile.

      By creating a system.profile collection in a replicated database and then restarting mongod, the startup code will downgrade the data files to 3.4 and refuse to start.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: