GODRIVER-3328Blocked

Make failpoints reliable in sharded clusters

h3. *Context* Failpoints currently aren't reliable on sharded clusters for multiple reasons, including: * {{mtest.SetFailPoint}} only sets a failpoint on one mongoS node by default. If a subsequent operation doesn't select the same mongoS, that can lead to non-deterministically failing tests because the failpoint isn't applied. * mongoS doesn't block for the full duration specified by {{blockTimeMS}}. See SERVER-96344. h3. *Definition of done* * Set failpoint on every mongoS in sharded cl

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
Testing
Labels
Tags and classification

No labels assigned.