[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: File enablesharding_repro.js    
Issue Links:
Duplicate
duplicates SERVER-16184 repeated WriteBackListener error on o... Closed
Related
is related to SERVER-16252 DBConnectionPool::flush should fully ... Closed
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:

Error: command { "enablesharding" : "test" } failed: {
        "code" : 13111,
        "ok" : 0,
        "errmsg" : "exception: error creating initial database config information :: caused by :: field not found, expected type 8"
}

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.

Generated at Thu Feb 08 03:39:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.