[SERVER-8771] Mongostat 2.2 can't --discover shards in a 2.4 cluster Created: 27/Feb/13  Updated: 11/Jul/16  Resolved: 01/Mar/13

Status: Closed
Project: Core Server
Component/s: Sharding, Tools
Affects Version/s: None
Fix Version/s: 2.2.4, 2.4.0-rc2

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:
  1. Bring up a 2.4 sharded cluster
  2. Run mongostat --discover with a 2.2 version of mongostat
Participants:

 Description   

Mongostat 2.4 supports --discover on both 2.2 and 2.4 clusters. Using a 2.2 version of mongostat with --discover on a 2.4 cluster it will only see the mongos and not mark it as a RTR.

We should probably either make 2.4 mongos work with a 2.2 mongostat or backport the change that makes mongostat work to 2.2.



 Comments   
Comment by auto [ 01/Mar/13 ]

Author:

{u'date': u'2013-03-01T23:25:16Z', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: SERVER-8771 Additional fix for mongostat --discover with mongos
Branch: v2.2
https://github.com/mongodb/mongo/commit/de7b456a97ed838c95023829687c7c91e5ddc1ee

Comment by auto [ 01/Mar/13 ]

Author:

{u'date': u'2013-03-01T23:25:16Z', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: SERVER-8771 Additional fix for mongostat --discover with mongos
Branch: master
https://github.com/mongodb/mongo/commit/6084f5cb58657f2576e5a63794fcf302b1777a8c

Comment by Spencer Brody (Inactive) [ 27/Feb/13 ]

The commit that would need to be backported to 2.2.4 is this: https://github.com/mongodb/mongo/commit/ddddf3b6a4bb3ff70fe12dd83e3ab0f43ffdd318

Comment by Spencer Brody (Inactive) [ 27/Feb/13 ]

The reason this broke was that there used to a section in serverStatus() called "shardCursorType" which was used by mongostat to determine whether or not it was talking to a mongos. This field was removed from serverStatus as part of the changes Eliot did to serverStatus to 2.4. In order to make 2.4 mongos work with 2.2 mongostat we'd have to add that field back in, but as the value that field was reporting is no longer even tracked, I assume eliot removed it for a reason. Given that, I think it makes more sense to just backport the fix to mongostat to 2.2.4 (it's a 1 line change) so that mongostat from 2.2.4 will be able to --discover on clusters running 2.4.

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