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

Do not propagate commit point through heartbeats when FCV=4.0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.10
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-03-25
    • Linked BF Score:
      17

      Description

      In SERVER-39367, we started propagating the majority commit point through heartbeats. This causes sync source cycles in mixed 4.2/4.0 replica sets, since 4.0 nodes will sync from a node with the same lastApplied if it has a higher lastOpCommitted. We will not propagate the commit point through heartbeats unless FCV=4.2, so that there are no 4.0 nodes in the set.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39367 lastOpCommitted being reset on restart can cause sync source cycle

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-33248 Allow choosing a sync source that we are up to date with if it has a higher lastOpCommitted

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

          Task - A task that needs to be done. SERVER-40194 Revert SERVER-33248 on 4.0

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

          Task - A task that needs to be done. SERVER-40211 Remove FCV check for propagating commit point through heartbeats

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

            Activity

              People

              Assignee:
              tess.avitabile Tess Avitabile
              Reporter:
              tess.avitabile Tess Avitabile
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: