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

Restore from 2.4 DB into 2.6 DB fails due to index?

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.6.0-rc0
    • Component/s: Tools
    • Labels:
      None
    • ALL
    • Hide

      Use this command and see screenshot.

      mongorestore --drop --db DB ".\DB"
      echo done

      Show
      Use this command and see screenshot. mongorestore --drop --db DB ".\DB" echo done

      It appears that if a 2.4 DB which was backed up using MongoDump is then restored via MongoRestore into 2.6 and that dump contains an index which is too large to index, then the restore stops and leaves the DB incompleted.

      Notice how the last line from MongoRestore is

      Error creating index LearningLine.Conversation: 17282 err: "Btree::insert: key too large to index, failing LearningLine.Conversation.$find_messages_by_activity 1426 { : { Attachments: [], LastAttachmentId: 0, C..."

      This is NOT the final collection to restore.

        1. C__WINDOWS_system32_cmd.exe (53).png
          C__WINDOWS_system32_cmd.exe (53).png
          43 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            mkennedy66996693 Michael Kennedy
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: