-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gc(ticdc): add min service gc safe point metrics #10553
gc(ticdc): add min service gc safe point metrics #10553
Conversation
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #10553 +/- ##
================================================
+ Coverage 57.5536% 57.8620% +0.3084%
================================================
Files 850 853 +3
Lines 126767 127403 +636
================================================
+ Hits 72959 73718 +759
+ Misses 48369 48229 -140
- Partials 5439 5456 +17 |
@flowbehappy: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest-required |
1 similar comment
/retest-required |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: asddongmen, CharlesCheung96, flowbehappy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest-required |
3 similar comments
/retest-required |
/retest-required |
/retest-required |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
/retest |
3 similar comments
/retest |
/retest |
/retest |
/retest |
3 similar comments
/retest |
/retest |
/retest |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
/test dm-compatibility-test |
/retest-required |
1 similar comment
/retest-required |
/test dm-compatibility-test |
/retest |
/test dm-compatibility-test |
…c-safepoint-metrics
/retest-required |
1 similar comment
/retest-required |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
Issue Number: ref #10463
What is changed and how it works?
ticdc uses min service gc safe point to check whether data is GCed, this PR adds min service gc safe point metrics to ticdc dashboard, and with this metric, the user can easily understand why changefeed failed with
ErrSnapshotLostByGC
errorCheck List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note