SERVER-14983Open

Ability to immediately mark the node as unable to service user queries

In production systems there is a common problem scenario when a particular underprovisioned mongod node becomes overloaded by a sudden load peak, causing service timeouts on the application level. In this case a plain retry strategy will add more load to the already overloaded system, frequently causing massive service degradation and prolonged periods of outage. The ideal, yet very complicated way to gracefully handle the situation is for drivers or mongoS to detect that the node is overloaded

Affected Versions
Versions known to exhibit this issue
2.6.4
Fixed Versions
Versions that include the fix
Needs Further Definition
Components
Server components related to this issue
ReplicationUsability
Labels
Tags and classification

No labels assigned.