[SERVER-34164] [support] add stats for database refresh to CatalogCache Created: 28/Mar/18  Updated: 07/Sep/23  Resolved: 07/Sep/23

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Antonio Fuschetto
Resolution: Done Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-80722 Rationalize Catalog Cache' statistics Backlog
related to SERVER-80724 Add database refresh statistics to Ca... Blocked
related to SERVER-80868 Complete TODO listed in SERVER-34164 Blocked
related to SERVER-52999 Complete TODO listed in SERVER-34164 Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18
Participants:

 Comments   
Comment by Antonio Fuschetto [ 05/Sep/23 ]

As discussed internally, statistics for database refresh events are definitely needed (SERVER-80724), but we need to streamline existing ones first (SERVER-80722) as they need to be clear to anyone other than a sharding expert and represented correctly by T2.

Comment by Esha Maharishi (Inactive) [ 01/Nov/20 ]

This is an old cleanup ticket that wouldn't be scheduled independently. It may get done as part of other work, or may become irrelevant once all collections and views are tracked in the sharding catalog.

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