Details
-
Task
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
Description
Differences in server status output meaning from replica sets to sharded clusters should be explicitly defined. For example, number of connections along with number of ops is specific to the mongos you run it on and not cluster-wide. As a result the implicit behavior and definitions are different when running on a replica set vs. a sharded cluster.
New metrics being added to serverstatus() for 2.4 should also be doced,
Config server oplog details should be doc'd as well.