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

db.upgradeCheck() does not perform checks in v3.0.x and v3.2.x

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.1
    • Component/s: Shell
    • None
    • Query
    • Fully Compatible
    • ALL

      Running 3.2.1 shell against a 2.4 MongoDB.

      $ mongo ...
      MongoDB shell version: 3.2.1
      connecting to: ...
      > db.upgradeCheck()
      database 'gravity-staging' for 2.6 upgrade compatibility
      ...
      Everything in 'gravity-staging' is ready for the upgrade!
      

      This isn't true, the import will fail with

      Failed: gravity-staging.featured_links: error creating indexes for gravity-staging.featured_links: createIndex error: Btree::insert: key too large to index, failing gravity-staging.featured_links.$subtitle_1 1040 { : "With his declaration that “painting relates to both art and life,” Robert Rauschenberg opened up the ivory tower that was postwar American paintin..." }
      

      The command also runs suspiciously fast.

      The 2.6.12 version of the command line client processes documents.

      $ mongo ...
      MongoDB shell version: 2.6.12-pre-
      connecting to: sawyer.mongohq.com:10007/gravity-staging
      > db.upgradeCheck()
      database 'gravity-staging' for 2.6 upgrade compatibility
      
      Checking database gravity-staging
      
      Checking collection gravity-staging.ab_test_groups
      
      Checking collection gravity-staging.access_controls
      28481 documents processed
      74362 documents processed
      115745 documents processed
      158064 documents processed
      202519 documents processed
      
      ...
      

      Will update once/if it finds my error.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            dblock Daniel Doubrovkine
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: