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?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Duplicate
    • Affects Version/s: 2.6.0-rc0
    • Fix Version/s: None
    • Component/s: Tools
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      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

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: