[SERVER-48608] Not found index after init sync Created: 05/Jun/20  Updated: 27/Oct/23  Resolved: 07/Jul/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.0.3
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Martin Polák Assignee: Dmitry Agranat
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

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!



 Comments   
Comment by Dmitry Agranat [ 07/Jul/20 ]

Hi martin.polak@unicorn.com,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,
Dima

Comment by Carl Champain (Inactive) [ 08/Jun/20 ]

Hi martin.polak@unicorn.com,

Can you please provide the full mongod.log file?

Kind regards,
Carl

Generated at Thu Feb 08 05:17:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.