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

Make sure to catch up to minValid before exiting rollback

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Major - P3
          • Resolution: Works as Designed
          • Affects Version/s: None
          • Fix Version/s: None
          • Component/s: Replication
          • Labels:
            None

            Description

            Not doing so can (among other problems) result in an "Unrecoverable rollback error" if the node ever rolls back a second time.

              Attachments

                Issue Links

                is related to

                Bug - A problem which impairs or prevents the functions of the product. SERVER-26570 MongoDB Slave Crashed During Replication

                • Critical - P2 - Crashes, loss of data, severe memory leak.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. SERVER-23070 rewrite SyncSourceResolver to select sync source asynchronously

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

                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:
                      2 Vote for this issue
                      Watchers:
                      8 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: