[SERVER-26420] Make internal clients identify themselves in the isMaster handshake Created: 30/Sep/16 Updated: 31/Oct/16 Resolved: 24/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2016-10-31 |
| Participants: |
| Description |
|
It will be helpful for a mongod to be able to distinguish connections from a mongos/mongod of a particular version from connections from applications. This identifying information could be helpful in order to ensure correctness when a cluster is running in a mixed-version configuration (i.e. during an upgrade or downgrade). When mongos or mongod initialize an outgoing connection, they should include an internalClient field in the isMaster command. This field has the following format:
In this way, the client communicates both that it is also a node in the cluster as well as the range of wire protocols which it supports. |
| Comments |
| Comment by Githook User [ 24/Oct/16 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |
| Comment by David Storch [ 20/Oct/16 ] |
|
Re-opening, since I discovered that the mongo shell is currently including internalClient information. |
| Comment by Githook User [ 20/Oct/16 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |