[SERVER-82933] Investigate potential gaps in FTDC and a loss in retention when introducing the embedded router collectors Created: 08/Nov/23  Updated: 05/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: pm-635-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-82034 Initialize the router FTDC controller... Open
Assigned Teams:
Catalog and Routing
Participants:

 Description   

When introducing more collectors to the FTDC machinery, there is the possibility to create gaps and a loss in retention. In other words, there are some heavy/intensive collectors (e.g. serverStatus) that will make the FTDC machinery to recollect data each time in a bigger interval, producing a regression in the dimension / richness of the data (more gaps). 

When introducing the embedded router collectors, for instance, the serverStatus will be called twice, one for the shard and one for the router, and this can reproduce the problems explained.

The goal of this ticket is to see if these cases are being reproduced and, if applies, how to solve them. 



 Comments   
Comment by Antonio Fuschetto [ 01/Dec/23 ]

Moving back to the backlog as there are new tickets for Milestone 1 having higher priority.

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