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

Rollback does not wait for applier to finish before starting

          Details

          • Backwards Compatibility:
            Fully Compatible
          • Operating System:
            ALL
          • Backport Completed:
          • Sprint:
            Repl E (01/08/16)

            Description

            This error message is a bit mislead as well. The error is due to trying to re-apply the last/current oplog entry again.

            [rsSync] Fatal assertion 34361 OplogOutOfOrder Attempted to apply an earlier oplog entry (ts: Dec 18 01:16:07:1) when our lastWrittenOptime was (term: 2, timestamp: Dec 18 01:16:07:1)

            After looking a bit more into this, I have found this sequence which caused the problem:

            • Chained replication
            • Failover with rollback
            • Chained replica starts rollback while still apply with buffered oplog entries

            Under these conditions it is race where this error occurs when the rollback happens during/before all the buffered oplog entries are applied.

              Attachments

                Issue Links

                is duplicated by

                Bug - A problem which impairs or prevents the functions of the product. SERVER-20466 Rollback and batch apply can each set minvalid independantly

                • Major - P3 - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. SERVER-21979 MongoD instance came down

                • Major - P3 - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. SERVER-22482 Cache growing to 100% followed by crash

                • Major - P3 - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. SERVER-23525 Mongo Replica Set unusable after Primary crashes with out of Memory, followed by Op Log out of Order on replica members

                • Major - P3 - Major loss of function.
                • Closed
                related to

                Bug - A problem which impairs or prevents the functions of the product. SERVER-25145 During rollback (or w/minvalid invalid) select sync source based on end OpTime

                • Major - P3 - Major loss of function.
                • Closed

                  Activity

                    People

                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      6 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: