-
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
server: ConnectionEvent error from plugins should not make TiDB exit #9889
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9889 +/- ##
================================================
- Coverage 77.2034% 67.1154% -10.088%
================================================
Files 405 385 -20
Lines 81635 80588 -1047
================================================
- Hits 63025 54087 -8938
- Misses 13939 21652 +7713
- Partials 4671 4849 +178 |
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
PTAL @jackysp |
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
/run-all-tests |
It looks like the error is completely discarded. Should it be logged first? |
It's already logged here https://github.com/pingcap/tidb/pull/9889/files#diff-91bbeda7eb98a7adc57b9e47e2cf5c2bR346 |
oh, good! It would be best to log the error where it is being dropped though. |
What problem does this PR solve?
When I am testing whitelist plugin, I find that whitelist check fail makes tidb exit. That completely unreasonable.
What is changed and how it works?
ConnectionEvent
error from plugins should not make TiDB exitCheck List
Tests
@lysu