-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
domain: avoit to print too many log if the ddl job of runaway table is not finished #52283
domain: avoit to print too many log if the ddl job of runaway table is not finished #52283
Conversation
…nished Signed-off-by: Cabinfever_B <cabinfeveroier@gmail.com>
Hi @CabinfeverB. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #52283 +/- ##
================================================
+ Coverage 70.7391% 71.0074% +0.2683%
================================================
Files 1491 1540 +49
Lines 440448 459566 +19118
================================================
+ Hits 311569 326326 +14757
- Misses 109378 113152 +3774
- Partials 19501 20088 +587
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you think we choose another way to fix, which is starting the runaway functionality after the bootstrap
pkg/domain/runaway.go
Outdated
for { | ||
select { | ||
case <-do.exit: | ||
return | ||
case <-runawayWatchSyncTicker.C: | ||
err := do.updateNewAndDoneWatch() | ||
if err != nil { | ||
logutil.BgLogger().Warn("get runaway watch record failed", zap.Error(err)) | ||
if now := time.Now(); now.Sub(lastLogErrorTime) > runawayLoopLogErrorInterval { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it OK to use count here? For example, runawayLoopLogErrorCnt = 300
Your idea is the best way, but I don't know much about the bootstrap process, so I'm not sure how to do. This is only a workaround. |
Signed-off-by: Cabinfever_B <cabinfeveroier@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest LGTM
pkg/domain/runaway.go
Outdated
return | ||
} | ||
} | ||
count++ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move this line after the if block so the first time enter this path should also print the log
pkg/domain/runaway.go
Outdated
for { | ||
select { | ||
case <-do.exit: | ||
return | ||
case <-runawayWatchSyncTicker.C: | ||
err := do.updateNewAndDoneWatch() | ||
if err != nil { | ||
logutil.BgLogger().Warn("get runaway watch record failed", zap.Error(err)) | ||
count++ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
Signed-off-by: Cabinfever_B <cabinfeveroier@gmail.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: glorv, lance6716 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 |
@CabinfeverB: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/test fast_test_tiprow |
@CabinfeverB: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
@CabinfeverB: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
/test unit-test |
@CabinfeverB: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
/run-cherry-picker |
In response to a cherrypick label: new pull request created to branch |
…nished
What problem does this PR solve?
Issue Number: close #52048
Problem Summary:
What changed and how does it work?
Check List
Tests
before
after
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.