[SERVER-53476] Don't include initial sync metrics in FTDC Created: 22/Dec/20  Updated: 06/Dec/22  Resolved: 22/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-53382 Add additional initial sync metrics t... Backlog
Duplicate
duplicates SERVER-47528 Presence of initialSyncStatus in repl... Closed
Related
is related to SERVER-47863 Initial Sync Progress Metrics Closed
Assigned Teams:
Replication
Operating System: ALL
Backport Requested:
v4.4, v4.2
Participants:

 Description   

SERVER-47863 introduced some initial sync metrics to replSetGetStatus, and therefore to FTDC. However those metrics include per-collection information, so if the user has a very large number of collections this can make each FTDC sample quite large. This will limit FTDC retention and also make the FTDC difficult to work with.

These metrics have limited value in FTDC since they are also logged, so we should suppress them by specifying initialSync:false at the point where FTDC collects replSetGetStatus.


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