[SERVER-6277] Reserve connections for replication Created: 02/Jul/12 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tyler Brock | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
Connections to mongod for the purposes of replication should have reserved connections so that the hard/soft connection limits do not affect replication mechanisms. |
| Comments |
| Comment by Dwight Merriman [ 01/Aug/12 ] |
|
makes sense. a related but different question is: what should replica sets do when members (eg primary) hit their connection limit? if clients are being pathological, failing over to another machine is inferior to just closing all connections. |