[SERVER-21067] Investigate having the storage size of a given collection/index/database cached within the WT/KV api Created: 22/Oct/15  Updated: 06/Dec/22  Resolved: 15/Apr/19

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

Type: Improvement Priority: Minor - P4
Reporter: David Hows Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-17675 Support file per database for WiredTiger Closed
related to SERVER-3181 Add option to listDatabases to only g... Closed
related to SERVER-21066 Investigate listDatabases option to r... Closed
is related to SERVER-20716 Slow listDatabases with WT Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Currently, we have to manually lookup how large a given collection/index is and for a database look up all collections/indexes to sum. Caching this data would cut down in cases where we have lots of collections/indexes/databases to review.


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