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

failCommand failpoint should ignore commands from replica set members

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.6, 4.1.7
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2018-06-04, Repl 2018-12-17

      Description

      When a secondary runs a command on the primary, it will trigger the failCommand failpoint. This is unexpected for drivers because we would like to use failCommand to test retryable writes and transactions on replica sets.

      Some options I see:

      1. change failCommand to ignore commands from replica set members
      2. change failCommand to ignore all commands except those in the sessionCheckoutWhitelist?
      3. drivers only use failCommand against single node replica sets or standalone servers
      4. drivers never use the "skip" and "times" options and instead configure the failpoint as "alwaysOn" or "off"

      A. Jesse Jiryu Davis, Spencer Brody

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jesse A. Jesse Jiryu Davis
              Reporter:
              shane.harvey Shane Harvey
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: