[SERVER-45659] Fatal Assertion 50923 at src/mongo/db/repl/replication_coordinator_impl.cpp 509 Created: 21/Jan/20  Updated: 24/Jan/20  Resolved: 24/Jan/20

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 4.0.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Anas Mansouri Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

got the following error, after a successful --repair on the secondary node.

2020-01-21T09:15:40.843-0600 W REPL     [free_mon] Rollback ID is not initialized yet.
2020-01-21T09:15:40.843-0600 I REPL     [initandlisten] Rollback ID is 2
2020-01-21T09:15:40.844-0600 F REPL     [initandlisten] This instance has been repaired and may contain modified replicated data that would not match other replica set members. To see your repaired data, start mongod without the --replSet option. When you are finished recovering your data and would like to perform a complete re-sync, please refer to the documentation here: https://docs.mongodb.com/manual/tutorial/resync-replica-set-member/
2020-01-21T09:15:40.844-0600 F -        [initandlisten] Fatal Assertion 50923 at src/mongo/db/repl/replication_coordinator_impl.cpp 509
2020-01-21T09:15:40.844-0600 F -        [initandlisten] 
 
 
***aborting after fassert() failure



 Comments   
Comment by Anas Mansouri [ 24/Jan/20 ]

thanks for the answer. I ended up forcing a resync.

Comment by Danny Hatcher (Inactive) [ 21/Jan/20 ]

As mentioned in our documentation on the --repair option, the feature does not work against a replica set member. You must follow our procedures on resyncing a replica set member.

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