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

Copydb breaks on (some) capped collections

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 2.6.1
    • None
    • 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

    Description

      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

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-13976 Cloner needs to detect failure to create collection

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-13737 CollectionOptions parser should skip "size"/"max" elements if values non-numeric

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-13968 Report invalid collection options in "<db>.system.namespaces" in upgrade checker

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              rassi J Rassi
              nstott Nick Stott
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: