[SERVER-21604] v3.0 mongos fails to ping config.mongos if config servers are v3.2 Created: 20/Nov/15  Updated: 25/Jan/17  Resolved: 25/Nov/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.2.0-rc3
Fix Version/s: 3.2.0-rc5

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-21586 Investigate v3.0 mongos and v3.2 clus... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding D (12/11/15)
Participants:

 Description   

This is because the ping update write command is being rejected by v3.2 config servers:

{ ok: 0, code: 2, errmsg: "w:1 and w:'majority' are the only valid write concerns when writing to config servers, got: { w: 0, wtimeout: 0 }" } 



 Comments   
Comment by Githook User [ 25/Nov/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-21604 v3.0 mongos fails to ping config.mongos if config servers are v3.2
Branch: master
https://github.com/mongodb/mongo/commit/4afeb91fb45bb343583a218e23b971cf7b3c33f1

Comment by Randolph Tan [ 21/Nov/15 ]

schwerin As far as I know, the only place that inspects the document in our code is the shell helpers for stop/start balancer. The helper might hang indefinitely (or hopefully timeout) waiting for the pings. I suspect our cloud services might also be mimicking the shell helper.

Comment by Andy Schwerin [ 20/Nov/15 ]

The config.mongos collection is purely diagnostic, right?

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