[SERVER-13711] Allow marking mongod as unavailable for new connections at mongos Created: 24/Apr/14 Updated: 10/Dec/14 Resolved: 09/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ruairi Newman (Inactive) | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
To facilitate taking down a shard member node non-disruptively in a production environment: In a production sharded configuration, where each shard consists of a replica set, provide functionality at the mongos to mark a shard primary as not available for new connections. Direct new connections to another shard member, while allowing existing connections to the Primary to complete. |
| Comments |
| Comment by Robert Jobson [ 09/Jul/14 ] |
|
What is needed here to move forward? We simply want to mark any node as not available for new connections at the router (mongos) level and allow any existing connections to complete before taking that node offline. |
| Comment by Greg Studer [ 09/Jul/14 ] |
|
Resolved as incomplete, feel free to reopen if more details can be provided. |
| Comment by Robert Jobson [ 24/Apr/14 ] |
|
Won't we need this for both the primaries and the secondaries in cases where the read preference is secondary or secondary preferred? |