[SERVER-81102] Mirrored Reads has its own client metadata showing up in $queryStats Created: 15/Sep/23  Updated: 08/Nov/23  Resolved: 08/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Memento Slack Bot Assignee: Backlog - Query Integration
Resolution: Works as Designed Votes: 0
Labels: querystats-7.1-qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-85096 TRACKING: M3 Correctness Tickets Closed
Assigned Teams:
Query Integration
Participants:

 Description   

Reported by jmo+mms@john-morales.com :

Mirrored reads (on by default since 4.4) result in quite few query stats entries on the secondaries. I suppose eventually all the access patterns on the primary will be observed as a queryStats entries on the secondaries, too. And further, these mirrored entries have the client metadata as mongod's internal client, rather than the customer's driver client metadata.

I suppose this could all be fine and expected behavior. From analysis point of view, they may not be the most interesting entries to include with analysis - but on the other hand, they do seem to be easily identifiable, so if nothing else our GTM/DW could just filter these out.

I think not having the customer's client metadata but rather mongod's client driver name of 'NetworkInterfaceTL-MirrorMaestro' was the main thing that caught my attention.


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