[SERVER-25514] prevent 3.4 config from adding a 3.2 shard during _configsvrAddShard Created: 09/Aug/16 Updated: 25/Jan/17 Resolved: 22/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | 3.3.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | 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 | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding 2016-08-29 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
check the wire version in the isMaster response in ShardingCatalogManagerImpl::_validateHostAsShard |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 09/Sep/16 ] |
|
Oh whoops, also I think these comments belong on |
| Comment by Esha Maharishi (Inactive) [ 09/Sep/16 ] |
|
nathan.myers, sounds like one of the processes might be crashing before the runCommand() is issued. Let's take a look at it on Monday morning. |
| Comment by Nathan Myers [ 09/Sep/16 ] |
|
Thus far I have not got any of the commands (insert, update, remove, find, count, aggregate, setShardVersion, ismaster) to fail as expected. When using runCommand(), I am often able to provoke a log warning about the mismatch, but the results are typically { "nInserted: 0, writeError: { "code" : 83, "errmsg": "write results unavailable...socket exception ..."}}. Using the ordinary e.g. "db.users.remove({})" forms, even the warning usually doesn't come up, or surfaces with [CONNECT_ERROR] instead. |
| Comment by Githook User [ 22/Aug/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |