-
Notifications
You must be signed in to change notification settings - Fork 500
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
remove some not very useful update events #1486
Conversation
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.
LGTM
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.
LGTM
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.
LGTM
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.
LGTM
/merge |
/run-all-tests |
@weekface merge failed. |
/run-all-tests |
/merge |
/run-all-tests |
cherry pick to release-1.1 in PR #1506 |
* remove some not very useful events * fix CI Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com>
What problem does this PR solve?
fixes: #1471
Now, there are too many
SuccessfulUpdate
events emitted bytidb-operator
, but they are not very useful.record.Event
method in client-go has aspamFilter
which is responsible for throttlingthe amount of events a source and object can produce.
So we'd better remove these not very useful
SuccessfulUpdate
events.What is changed and how does it work?
Check List
Tests
Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?: