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

Initial sync failed again and again due to unique index conflict

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 3.4.6
    • None
    • Replication
    • None
    • ALL

    Description

      Hi, 

      I encountered a problem when initial sync failed due to unique index conflict, and it can not be recovered, the error messages are as below:

       

      2018-06-28T17:53:32.046+0800 I REPL [initandlisten] Replaying stored operations from { ts: Timestamp 1530177067000|2, t: 6 } (exclusive) to { ts: Timestamp 1530177100000|62, t: 7 } (inclusive).
      2018-06-28T17:53:32.047+0800 F STORAGE [initandlisten] Unique index cursor seeing multiple records for key { : "423925:333C49:2397ED:e000", : "com.allfootballapp.news" }
      2018-06-28T17:53:32.047+0800 I - [initandlisten] Fatal Assertion 28608 at src/mongo/db/storage/wiredtiger/wiredtiger_index.cpp 974

       

      Please help!

      Attachments

        1. mongod.log
          412 kB
        2. rsconf.md
          1 kB

        Activity

          People

            eric.sedor@mongodb.com Eric Sedor
            zhcn381 CenZheng
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: