[SERVER-73037] Expose Sharded Collection Defragmentation Usage Created: 19/Jan/23  Updated: 26/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Matt Panton Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

Background
With the release of MongoDB version 6.0 defragmentation was released as a new feature for sharded clusters to reduce the impact of the metadata refresh. Currently it's not possible to track the usage of the defragmentation. It would be beneficial to the sharding team and customers if it's possible to track if a cluster has initiated defragmentation and the outcome.

 

 


Generated at Thu Feb 08 06:23:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.