-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-05-07
To aid testing, especially for drivers, we should have a failpoint that can induce arbitrary command failures.
Configuring such a failpoint would look like:
node.adminCommand({ configureFailPoint: 'failCommand', mode: 'alwaysOn', data: { closeConnection: false, // If true, closes the current socket when the fail point is hit errorCode: ErrorCodes.NotMaster // If set, causes the command to return the given code without actually executing. Incompatibile with 'closeConnection' } });
This failpoint will not be triggered for isMaster, configureFailPoint, or buildinfo.
- is duplicated by
-
SERVER-34187 FailPoint to hang up on client in abortTransaction/commitTransaction
- Closed
-
SERVER-34057 Update onPrimaryTransactionalWrite fail point for multi-statement transactions
- Closed
- is related to
-
SERVER-34943 failCommand failpoint should ignore commands from replica set members
- Closed
- related to
-
SERVER-5587 Command to close current connections
- Closed
-
SERVER-35083 Extend failCommand to return write concern errors
- Closed