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

Not found index after init sync

    • Type: Icon: Question Question
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.3
    • Component/s: None
    • None

      Hello, 

      i just did complete data recovery on secondary node with init sync. Everything looks fine, master node says secondary node is 1s behind the primary.

      But I found quite a lot strange logs on that secondary node:

      W STORAGE [repl writer worker 5] RecordId(3403) not found in the index for key \{ : "959e7ee019b0460a819438b6e7a5c7ff", : "jobScheduler" }
      
      W STORAGE [repl writer worker 14] RecordId(3404) not found in the index for key \{ : "401dd4f2d0294ea995589405eab7461a", : "jobScheduler" }
      
      W STORAGE [repl writer worker 11] RecordId(3503) not found in the index for key \{ : "959e7ee019b0460a819438b6e7a5c7ff", : "synchronizeCPOStates" }
      
      W STORAGE [repl writer worker 1] RecordId(3505) not found in the index for key \{ : "d8bc9411e74f42658f5d0b387a52b8cd", : "synchronizeCPOStates" }
      

       

      Can you tell me what could have gone wrong? I'm using secondary node for backuping whole cluster, but if this can be some data corruption, it can be bad for me.

       

      Thank you!

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            martin.polak@unicorn.com Martin Polák
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: