-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Minor Change
-
v4.0
-
Repl 2018-06-04, Repl 2018-12-17
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:
- change failCommand to ignore commands from replica set members
- change failCommand to ignore all commands except those in the sessionCheckoutWhitelist?
- drivers only use failCommand against single node replica sets or standalone servers
- drivers never use the "skip" and "times" options and instead configure the failpoint as "alwaysOn" or "off"
- is depended on by
-
DRIVERS-405 Retryable Reads
- Development Complete
- is related to
-
SERVER-38188 Create split brain passthroughs
- Backlog
-
SERVER-34960 Add a way to enter a failpoint without decrementing 'times' or 'skip'
- Closed
-
SERVER-35004 Add functionality to only fail specific command(s) in failCommand failpoint
- Closed
- related to
-
SERVER-34551 Add failpoint to fail commands with network errors or arbitrary error codes
- Closed