[SERVER-19527] Configuration directive changes for config servers as replica sets Created: 22/Jul/15 Updated: 25/Jan/17 Resolved: 27/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 7 08/10/15, Sharding 8 08/28/15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
To support upgrading to replica-set config servers (csrs) from existing deployments of sync cluster config servers (sccc), we must add a new configuration directive, sharding.configsvrMode and command line option, --configsvrMode=sccc. This directive is only legal on mongod and only if the --configsvr directive has been set. Servers started with --configsvr and --confisvrMode=sccc act as an SCCC config server rather than a CSRS config server, even if the node is a member of a replica set. This flag’s only practical effect is to affect the response the node sends during ismaster handshake. "sccc" is the only viable argument to --configsvrMode. --configsvrMode=csrs is implied by starting with --configSvr and --replSet. This flag allows suppression of that implied behavior during the CSRS upgrade process. |
| Comments |
| Comment by Andy Schwerin [ 04/Aug/15 ] |
|
The correct value for not "csrs" is "sccc" for "sync cluster connection config", not "scc". |
| Comment by Githook User [ 30/Jul/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |