[SERVER-15938] Running enablesharding using 2.8 mongods with 2.6 mongos fails with obscure message Created: 04/Nov/14 Updated: 23/Mar/15 Resolved: 24/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrew Emil (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If you have a sharded cluster with 2.8 mongod shards and a 2.6 mongos, running enablesharding will result in a very confusing message:
It would be nice if there was a way to detect this situation and alert users to the fact that they need to upgrade all their mongos instances before any of their mongod instances. |
| Comments |
| Comment by Greg Studer [ 05/Nov/14 ] |
|
We'll see what we can do here - it isn't possible to change mongos 2.6 behavior and there's not always a distinguishable handshake with the shard. |