Details
Description
The help option on mongostat indicates that for running it against a replica set, the set name must be specified. However, that does not seem to work in 2.2.
$ mongostat --help | grep -A 1 host
|
-h [ --host ] arg mongo host to connect to ( <set name>/s1,s2 for
|
sets)
|
As per the help page -
mark-mbp:rs2 hillickm$ mongostat -h "test/127.0.0.1:47017,127.0.0.1:47018,127.0.0.1:47019"
|
|
|
insert query update delete getmore command flushes mapped vsize res faults locked db idx miss % qr|qw ar|aw netIn netOut conn set repl time
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:28
|
127.0.0.1:47019 *0 *0 *0 *0 0 3|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 346b 2k 3 test SEC 14:53:28
|
test/127.0.0.1:47017 socket exception [CONNECT_ERROR] for test/127.0.0.1:47017
|
|
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:29
|
127.0.0.1:47019 *0 *0 *0 *0 0 3|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 346b 2k 3 test SEC 14:53:29
|
test/127.0.0.1:47017 socket exception [FAILED_STATE] for test/127.0.0.1:47017
|
|
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:30
|
127.0.0.1:47019 *0 *0 *0 *0 0 1|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 62b 2k 3 test SEC 14:53:30
|
test/127.0.0.1:47017 socket exception [CONNECT_ERROR] for test/127.0.0.1:47017
|
|
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:31
|
127.0.0.1:47019 *0 *0 *0 *0 0 3|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 346b 2k 3 test SEC 14:53:31
|
test/127.0.0.1:47017 socket exception [FAILED_STATE] for test/127.0.0.1:47017
|
Without the RS name -
mark-mbp:rs2 hillickm$ mongostat -h "127.0.0.1:47017,127.0.0.1:47018,127.0.0.1:47019"
|
|
|
insert query update delete getmore command flushes mapped vsize res faults locked db idx miss % qr|qw ar|aw netIn netOut conn set repl time
|
127.0.0.1:47017 0 0 0 0 0 2 0 464m 3.36g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 7 test PRI 14:53:37
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:37
|
127.0.0.1:47019 *0 *0 *0 *0 0 1|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 62b 2k 3 test SEC 14:53:37
|
|
|
127.0.0.1:47017 0 0 0 0 0 2 0 464m 3.36g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 7 test PRI 14:53:38
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:38
|
127.0.0.1:47019 *0 *0 *0 *0 0 1|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 62b 2k 3 test SEC 14:53:38
|
|
|
127.0.0.1:47017 0 0 0 0 0 2 0 464m 3.36g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 7 test PRI 14:53:39
|
127.0.0.1:47018 *0 *0 *0 *0 0 2|0 0 464m 3.35g 21m 0 local:0.0% 0 0|0 0|0 204b 2k 3 test SEC 14:53:39
|
127.0.0.1:47019 *0 *0 *0 *0 0 1|0 0 272m 3.01g 5m 0 local:0.0% 0 0|0 0|0 62b 2k 3 test SEC 14:53:39
|
So this is either a bug in the tool or one in the help page. If it's the latter, the DOCS need to be updated also.
Attachments
Issue Links
- related to
-
TOOLS-107 mongorestore w/replicaset-connection fails with socket timeout
-
- Closed
-