[SERVER-60029] Hide wiredTiger['block-manager'] for sharded cluster Created: 16/Sep/21  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Sergei Timoshtshuk Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: sharding, sharding-nyc-subteam2, sharding-wfbf-sprint, wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Participants:
Case:
Story Points: 2

 Description   

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
 },

 


Generated at Thu Feb 08 05:48:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.