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

Fatal Assertion 50923 at src/mongo/db/repl/replication_coordinator_impl.cpp 509

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.10
    • Component/s: Internal Code
    • None
    • ALL

      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
      

            Assignee:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Reporter:
            anas.mansouri10@gmail.com Anas Mansouri
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: