[SERVER-26464] Poor compression of diagnostic data when secondary falls off the oplog Created: 05/Oct/16  Updated: 08/Sep/20  Resolved: 08/Sep/20

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

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

Issue Links:
Duplicate
duplicates SERVER-34864 String-valued fields should not parti... Closed
Related
is related to SERVER-27230 Poor compression of diagnostic data w... Closed
Operating System: ALL
Sprint: Security 2020-09-21
Participants:

 Description   

When the secondary falls off the oplog there are frequent schema changes in the diagnostic data (every few seconds) which results in very poor compression and much reduced retention period for diagnostic data.

The cause is that the replica set status infoMessage field with the string "could not find member to sync from" comes and goes periodically about every 5 seconds.

I believe this could be fixed by ignoring fields that do not contribute to ftdc data, such as strings, before comparing the schema of the current sample with the reference sample, instead of ignoring them after the comparison.



 Comments   
Comment by Mark Benvenuto [ 08/Sep/20 ]

SERVER-34864 did the work to ignore changes from fields that are not part of the FTDC compression payload.

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