Orphaned system.buckets collections

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc3, 5.1.0-rc0
    • Affects Version/s: 5.0.0-rc0
    • Component/s: None
    • Fully Compatible
    • ALL
    • v5.0
    • Hide 
       > db.createCollection('coll1' )
{ "ok" : 1 }
 > show collections
 coll1
 > 
 > db.createCollection('coll1', { timeseries: \\{ timeField: 'ts' }} )
{ "ok" : 0, "errmsg" : "Collection already exists. NS: test.coll1", "code" : 48, "codeName" : "NamespaceExists" }
> 
 > show collections
 coll1
 system.buckets.coll1
 > 
 > db.coll1.drop()
 true
 > 
 > show collections
 system.buckets.coll1
      Show
      > db.createCollection('coll1' ) { "ok" : 1 } > show collections coll1 > > db.createCollection('coll1', { timeseries: \\{ timeField: 'ts' }} ) { "ok" : 0, "errmsg" : "Collection already exists. NS: test.coll1", "code" : 48, "codeName" : "NamespaceExists" } > > show collections coll1 system.buckets.coll1 > > db.coll1.drop() true > > show collections system.buckets.coll1
    • Execution Team 2021-06-28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a path where a system.buckets collection can be orphaned if a previously created collection shares the namespace of a proposed createCollection with timeseries options. This bug can likely be addressed in the createCollection path for timeseries where a system.buckets collection is created prior to any namespace checking for existing collections. 

              Assignee:
              Henrik Edin
              Reporter:
              Michael Gargiulo
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: