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

Report upstream progress when initial sync completes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.0.3
    • Fix Version/s: 3.0.4
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      RPL 5 06/26/16

      Description

      Currently, write concern can fail to be satisfied even when sufficient nodes receive the write, if one of the nodes received it while initial syncing. Consider the following:

      • 2 nodes started as a replicaset
      • replSetInitiate is ran and the set is then hammered with w:2 writes
      • one node becomes primary and accepts a write
      • the other node receives the write through initial sync and does not report this progress

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19244 Secondary position information can be erroneous if nodes leave and rejoin a cluster with less data than before

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17934 Do not report upstream progress while in state STARTUP2

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

          Task - A task that needs to be done. SERVER-18110 Add Reporter to Data Replicator

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: