Copydb breaks on (some) capped collections

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.1
    • Component/s: Storage
    • None
    • ALL
    • Hide

      1. in 2.4.x, create a capped collection as above
      2. upgrade to 2.6
      3. run a copydatabase onto a new 2.6 instance

      Show
      1. in 2.4.x, create a capped collection as above 2. upgrade to 2.6 3. run a copydatabase onto a new 2.6 instance
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      capped collections in earlier versions of mongodb (2.4.x) can sometimes look like this:
      { "name" : "test-1.two", "options" :

      { "create" : "two", "size" : 1000000, "max" : "", "capped" : true, "autoIndexId" : true }

      },
      when a database with a capped collection like that is upgraded to 2.6.1, and then a copydatabase is run against it, the copy database succeeds, but the capped collections are not copied properly

              Assignee:
              J Rassi (Inactive)
              Reporter:
              Nick Stott
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: