[SERVER-9508] Shards not discovered by mongostat in 2.4.3 Created: 30/Apr/13  Updated: 15/Nov/21  Resolved: 21/Oct/13

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 2.4.3
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Dan Cooper Assignee: Randolph Tan
Resolution: Cannot Reproduce Votes: 0
Labels: mongostat
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 6.3


Operating System: Linux
Participants:

 Description   

Hello,

Since upgrading to 2.4.3, shards are no longer discovered when using mongostat. Example:

How it looks now with Mongo 2.4.3 and mongostat 2.4.3

[ec2-user@mng2ld ~]$ mongostat --host machine_name --discover --all --vvvvv
 
                insert  query update delete getmore command mapped  vsize    res non-mapped faults locked % idx miss %  netIn netOut  conn       time
 
rsgxxxvcs1ld         0      0      0      0       0       1     0m    70m    14m        70m      0        0          0    62b   786b     3   00:14:59
 
 
 
rsgxxxvcs1ld         0      0      0      0       0       1     0m    70m    14m        70m      0        0          0    62b   786b     3   00:15:00
 
 
 
rsgxxxvcs1ld         0      0      0      0       0       1     0m    70m    14m        70m      0        0          0    62b   786b     3   00:15:01
 
 
 
rsgxxxvcs1ld         0      0      0      0       0       1     0m    70m    14m        70m      0        0          0    62b   786b     3   00:15:02
 
 
 
rsgxxxvcs1ld         0      0      0      0       0       1     0m    70m    14m        70m      0        0          0    62b   786b     3   00:15:03
 

[ec2-user@mng2ld ~]$ mongostat --version

mongostat version 2.4.3

How it’s supposed to look (this is with Mongo 2.2.0)

-sh-4.1$ mongostat --version
 
mongostat version 2.2.0
 
                                                         insert  query update delete getmore command flushes mapped  vsize    res faults            locked db idx miss %   
 
mng1dv.taketwo.online:27017            0    181     26      0      37       5       0  6.04g  18.2g  3.32g      0    presence_dev:0.2%          0       0|0     0|0    29k    35k   302 rsgxxxset1  PRI   20:17:44
 
rmng2dv.taketwo.online:27017           *0     *0    *25     *0       0     2|0       0  10.8g  22.8g  2.57g      0    presence_dev:0.7%          0       0|0     0|0   226b     3k   174 rsgxxxset1  SEC   20:17:44
 
mng3dv.taketwo.online:27017            0      2      2      0       3       5       0  7.29g  15.7g  2.71g      0       cloud_dev:0.2%          0       0|0     0|0     8k    16k   296 rsgxxxset2  PRI   20:17:44
 
mng4dv.taketwo.online:27017           *0     *0     *1     *0       0     3|0       0  7.54g    16g  2.27g      0               .:0.1%          0       0|0     0|0   387b     4k   174 rsgxxxset2  SEC   20:17:44
 
                     rsgxxx6dv            0     32     14      0       0       5                  301m   186m      5                                                       5k     3k    48             RTR&a mp;a mp;n bsp;  20:17:44



 Comments   
Comment by Daniel Pasette (Inactive) [ 24/Jul/13 ]

dan.cooper, we haven't had any luck reproducing with 2.4.3 except in the case that renctan mentioned, which is when there is a cluster with no shards added.

If this is still a problem, can you attach the contents of the config.shards collection? This is how the --discover option discovers the members of the cluster.

Comment by Randolph Tan [ 27/Jun/13 ]

I tried setting up a cluster through AWS (instead of doing all machines locally) and was still unable to reproduce the issue. I was only able to reproduce it when I have a fresh config server that has an empty config.shards collection.

Comment by Dan Cooper [ 26/Jun/13 ]

Yes all 2.4.3

Comment by Randolph Tan [ 26/Jun/13 ]

Sorry, I forgot to ask the versions of the mongos, shards and config servers. Are they also all in 2.4.3?

Comment by Dan Cooper [ 26/Jun/13 ]

1. Are you using auth or keyFile? - none
2. Are your servers setup with ssl? If yes, can you give more details? - no
3. Are you running the mongostat local or remote relative to the mongos? - remote

Oddly it works with other versions of mongostat. Just not 2.4.3

Comment by Randolph Tan [ 26/Jun/13 ]

Hi,

I have trouble replicating this issue. Do you mind providing more details on your setup? For example:

1. Are you using auth or keyFile?
2. Are your servers setup with ssl? If yes, can you give more details?
3. Are you running the mongostat local or remote relative to the mongos?

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