Unreplicated db.system.profiling may cause DatabaseDifferCase

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • ALL
    • Hide

       

      // At this point, 'mydb' or 'MyDb' database doesn't exist yet

// secondary node
use mydb
db.setProfilingLevel(2)

// primary node
use MyDb
db.createCollection("coll") //< will throw a DatabaseDifferCase error on the secondary node
      Show
        // At this point, 'mydb' or 'MyDb' database doesn't exist yet // secondary node use mydb db.setProfilingLevel(2) // primary node use MyDb db.createCollection( "coll" ) //< will throw a DatabaseDifferCase error on the secondary node
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, the <db>.system.profiling collection is not replicated, which means it is possible to create an unreplicated database on a specific node in a replica set.

      If the same database is later created on other nodes using different casing, that node will fail with a DatabaseDifferCase error, while the rest of the nodes in the replica set will succeed.

            Assignee:
            Sam Mercier
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated: