-
Notifications
You must be signed in to change notification settings - Fork 288
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
kv-client(cdc): add more logs to help debug slow regions (#9981) #9983
Merged
ti-chi-bot
merged 3 commits into
pingcap:release-7.1
from
ti-chi-bot:cherry-pick-9981-to-release-7.1
Nov 16, 2023
Merged
kv-client(cdc): add more logs to help debug slow regions (#9981) #9983
ti-chi-bot
merged 3 commits into
pingcap:release-7.1
from
ti-chi-bot:cherry-pick-9981-to-release-7.1
Nov 16, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ti-chi-bot
added
lgtm
release-note-none
Denotes a PR that doesn't merit a release note.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
type/cherry-pick-for-release-7.1
This PR is cherry-picked to release-7.1 from a source PR.
labels
Nov 1, 2023
Signed-off-by: qupeng <[email protected]>
Signed-off-by: qupeng <[email protected]>
hicqu
force-pushed
the
cherry-pick-9981-to-release-7.1
branch
from
November 8, 2023 07:17
a0e7626
to
9216167
Compare
ti-chi-bot
bot
added
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
and removed
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
labels
Nov 8, 2023
ti-chi-bot
added
the
cherry-pick-approved
Cherry pick PR approved by release team.
label
Nov 8, 2023
hicqu
approved these changes
Nov 8, 2023
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hicqu 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 |
Signed-off-by: qupeng <[email protected]>
/retest |
hicqu
pushed a commit
to hicqu/ticdc
that referenced
this pull request
Nov 22, 2023
sdojjy
pushed a commit
to sdojjy/tiflow
that referenced
this pull request
Jan 6, 2024
sdojjy
added a commit
that referenced
this pull request
Jan 6, 2024
…) (#10425) close #9980 Co-authored-by: Ti Chi Robot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
cherry-pick-approved
Cherry pick PR approved by release team.
lgtm
release-note-none
Denotes a PR that doesn't merit a release note.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
type/cherry-pick-for-release-7.1
This PR is cherry-picked to release-7.1 from a source PR.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #9981 .
Also contains some base commits.
What problem does this PR solve?
Issue Number: close #9980
What is changed and how it works?
add more logs to help debug slow regions.
Check 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