SERVER-96344Open

mongos doesn't honor a failpoint's full blockTimeMS

The behavior of {{MaxTimeMSExpired}} differs between mongod and mongos when using a blocking failpoint: - mongod: Returns {{MaxTimeMSExpired}} after {{max(blockTimeMS, maxTimeMS)}}. - mongos: Returns {{MaxTimeMSExpired}} after maxTimeMS only. Repro: https://gist.github.com/prestonvasquez/d4b8193b4f67750994051ca61d8f035a results for mongos: results for mongod: Failpoints should be uniform across topologies, behaving as mongod does. In particular, (for sharded clusters) drivers

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 Infrastructure
Labels
Tags and classification
9.0-api-paritysp-customer-ticketsp-infinite-burndownsp-quick-wins