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

Do not silently ignore read errors when syncing a replica set node

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.4.8
    • 2.6.6, 2.7.8
    • Replication, Stability
    • None
    • Minor Change

    Description

      When a new clean node is being added to a replica set, if the source for initial sync has corrupted data, it seems that we try to sync whatever we can, silently ignoring all the records we can not fetch.

      While this "best effort" behavior makes sense, it can lead to significant data inconsistency within the replica set. We should not ignore data access errors during initial sync.

      example behavior (PRIMARY is the node with corruption in dummy.acl namespace, SECONDARY is the newly synced secondary):

      X:SECONDARY> rs.slaveOk()
      		 
      X:SECONDARY> use dummy
      		 
      switched to db dummy
      		 
      X:SECONDARY> db.acl.count()
      		 
      101
      		 
      X:SECONDARY> exit
      		 
      bye
      		 
      AD-MAC10G:ff alexander$ mongo
      		 
      MongoDB shell version: 2.4.8
      		 
      connecting to: test
      		 
      X:PRIMARY> use dummy
      		 
      switched to db dummy
      		 
      X:PRIMARY> db.acl.count()
      		 
      10002
      		 
      X:PRIMARY> exit
      		 
      bye

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17903 When corruption detected, server continues to run and sync secondaries

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

          Task - A task that needs to be done. DOCS-4315 Document that documents will be skipped in initial replSet sync if source has corrupt data

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

          Task - A task that needs to be done. SERVER-1558 Documents should write checksum on write, verify checksum on read

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17903 When corruption detected, server continues to run and sync secondaries

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

          Activity

            People

              milkie@mongodb.com Eric Milkie
              alex.komyagin@mongodb.com Alexander Komyagin
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: