-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
(copied to CRM)
-
2
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
When you run db.collection.stats() command on sharded cluster top level wiredTiger.block-manager data always shows first shard metrics. This can be confusing and ideally should not be visible.
Top-Level Stats:
"block-manager" : { "allocations requiring file extension" : 1279, "blocks allocated" : 1366, "blocks freed" : 28, "checkpoint size" : 27422720, "file allocation unit size" : 4096, "file bytes available for reuse" : 61440, "file magic number" : 120897, "file major version number" : 1, "file size in bytes" : 27500544, "minor version number" : 0 },
Shard-0:
"block-manager" : { "allocations requiring file extension" : 1279, "blocks allocated" : 1366, "blocks freed" : 28, "checkpoint size" : 27422720, "file allocation unit size" : 4096, "file bytes available for reuse" : 61440, "file magic number" : 120897, "file major version number" : 1, "file size in bytes" : 27500544, "minor version number" : 0 },
Shard-1:
"block-manager" : { "allocations requiring file extension" : 3812, "blocks allocated" : 18244, "blocks freed" : 15680, "checkpoint size" : 39616512, "file allocation unit size" : 4096, "file bytes available for reuse" : 42553344, "file magic number" : 120897, "file major version number" : 1, "file size in bytes" : 82186240, "minor version number" : 0 },