[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:
Duplicate
duplicates SERVER-3110 unlimited nonvoting nodes in replica set Closed
Participants:

 Description   

At the moment, max number of members in replica set is 50.
Could this be unlimited or configurable?
Out customers want to synchronize data between more then 50 offices, and we can`t do it with Mongo now.
Also, need this for config servers replica set too.



 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
-Viacheslav

Comment by Kaloian Manassiev [ 23/Nov/16 ]

Hi viacheslav.kulyk@avid.com,

With regard to your comment

Also, need this for config servers replica set too.

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,
-Kal.

Comment by Kelsey Schubert [ 23/Nov/16 ]

Hi vkulyk,

Thank you for opening this improvement request. I've marked it as a duplicate of SERVER-3110 since I believe it provides the functionality you are looking for. Please feel free to vote for SERVER-3110 and watch it for updates.

Kind regards,
Thomas

Generated at Thu Feb 08 04:14:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.