[SERVER-65289] Improvements to Mirrored Reads Metrics and Visibility Created: 06/Apr/22 Updated: 09/Nov/23 Resolved: 27/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.6, 4.4.13 |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Diego Rodriguez (Inactive) | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 6.1-targeted, diagnosibility, troubleshooting | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
Hi Team, Starting in v4.4 we introduced the Mirrored Reads feature, and we have a couple of server metrics tracking that:
The problem is that there is no indication in the Secondaries' Diagnostic Data or Logs of the amount of reads executed as a result of the Mirror Reads feature. For Troubleshooting purposes, it would be nice to have the following:
These changes should be very helpful when troubleshooting, and the suggested changes should be added to both v4.4 and v5.0. |
| Comments |
| Comment by Alex Li [ 24/Oct/22 ] |
|
The mirroredReads.received metric is now changed to mirroredReads.processedAsSecondary to provide a more accurate name. |
| Comment by Jason Chan [ 27/Jun/22 ] |
|
This patch adds the following:
|
| Comment by Githook User [ 24/Jun/22 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |