[SERVER-27169] Maximum number of members in replica set should not be limited to 50 Created: 23/Nov/16 Updated: 23/Nov/16 Resolved: 23/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Viacheslav Kulyk | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
At the moment, max number of members in replica set is 50. |
| Comments |
| Comment by Viacheslav Kulyk [ 23/Nov/16 ] |
|
Hi, Thank you for a quick response. As for config servers, we need this to be able to restart mongos on 50+ node, when node is network disconncted. This will be possible, when https://jira.mongodb.org/browse/SERVER-23398 is solved + config servers replica set can have more than 50 members Regards |
| Comment by Kaloian Manassiev [ 23/Nov/16 ] |
|
With regard to your comment
Do you mind giving us a little bit of detail for the use case where you need such a large number of config server replica set nodes? Thank you in advance. Best regards, |
| Comment by Kelsey Schubert [ 23/Nov/16 ] |
|
Hi vkulyk, Thank you for opening this improvement request. I've marked it as a duplicate of Kind regards, |