Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0-rc12, 4.7.0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.4
Sprint:
Service arch 2020-06-29

There are a lot of different conditions where the failCommand failpoint can activate. We should add logging to make it obvious why it happened.

causes

SERVER-49220 failCommand with appName does not fail connection handshake command

Closed

is depended on by

SERVER-48932 ReplicaSetMonitor hitting failpoint set during drivers test

Closed

Assignee:: Benjamin Caimano (Inactive)

Reporter:: Benjamin Caimano (Inactive)

Participants:: Benjamin Caimano, Githook User

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Jun 18 2020 10:46:20 PM UTC

Updated:: Oct 29 2023 10:06:43 PM UTC

Resolved:: Jun 26 2020 08:45:01 PM UTC