- 
    Type:Improvement 
- 
    Resolution: Won't Do
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: Networking, Replication
- 
    None
- 
        Service Arch
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
In the case when `mongod` hits connection limit it stops accepting connection both from clients and from other replicas in its replicaset.
When something particularily bad happens on MongoDB replicaset and `mongod` exhausts connection limit, the only way to restore replicaset service is to restart all `mongod` processes.
I consider `--maxConns` in its current state harmful for replicasets. I propose two ways for fixing the issue:
1. Either reserve some quota for replicas or by any other means move connections from replicas out of connection limit.
2. Forbid usage of `--maxConns` for replicasets.
- duplicates
- 
                    SERVER-34884 Replication executor creates connection storm which should be limited -         
- Closed
 
-