[DocDB] Incorrect Aggregation Function for certain xCluster Metrics: Change from Sum to Max #25422
Open
1 task done
Assignees
Labels
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
priority/medium
Medium priority issue
status/awaiting-triage
Issue awaiting triage
Comments
yusong-yan
added
area/docdb
yugabyte-ci
added
kind/bug
yusong-yan
changed the title
1 task
yusong-yan
added a commit
that referenced
this issue
Dec 26, 2024
…etrics from Sum to Max Summary: `kSum` aggregation is currently used for many xCluster metrics, but this leads to overflows and inaccuracies for metrics like `last_read_hybridtime`, which should instead use maximum aggregation `kMax`. Next Step [[ #25437 | #25437 ]]: For optimal accuracy in the future, we should implement a `kLatest` aggregation function, which would require metric storing both the latest value and its corresponding timestamp. Jira: DB-14654 Test Plan: Jenkins Reviewers: hsunder, xCluster, jhe Reviewed By: jhe Subscribers: rthallam, ybase, ycdcxcluster, slingam Differential Revision: https://phorge.dev.yugabyte.com/D40873
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jira Link: DB-14654
Description
kSumaggregation is currently used for many xCluster metrics, but this leads to overflows and inaccuracies for metrics like last_read_hybridtime, which should instead use maximum aggregationkMax.For optimal accuracy in the future, we should implement a
kLatestaggregation function, which would require metric storing both the latest value and its corresponding timestamp.Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: