[SERVER-19539] Provide data in the ismaster handshake to identify the config server protocol Created: 23/Jul/15 Updated: 09/Feb/17 Resolved: 05/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Task | 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 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
To support upgrade to config servers as replica sets (CSRS) from sync cluster connection config servers (SCCC), it is necessary for shard servers and mongos nodes to dynamically switch their catalog manager implementation based on the config server protocol reported by the config servers. To this end, config servers running the CSRS protocol should report a new top level field in their response to ismaster, configsvr: 1 to indicate that shard and mongos nodes should communicate with the config servers using the config server replica set protocol version 1. If the field is missing or has value 0, those nodes should instead communicate using the SCCC protocol. |
| Comments |
| Comment by Githook User [ 05/Aug/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 05/Aug/15 ] |
|
Needs to include configsvr:0 when running in SCCC mode. |
| Comment by Githook User [ 31/Jul/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |