-
Notifications
You must be signed in to change notification settings - Fork 409
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
*: Refine some logging level (release-6.5) #6846
*: Refine some logging level (release-6.5) #6846
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
@JaySon-Huang: This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved by the collaborators. AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review. 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-all-tests |
/hold seems not needed for release-6.5 so far |
replaced by #8558 |
cherry-pick of #6844 to release-6.5
What problem does this PR solve?
Issue Number: ref #6845
Problem Summary:
With logging level "info",
Before this PR when there is no write && read on tiflash, there are more than 15 logging every 30 seconds
After this PR, when there is no write && read, there is only 2 logging every 10 minutes
What is changed and how it works?
Poco::Logger
withDB::Logger
flash.replica_read_max_thread
Check List
Tests
Side effects
Documentation
Release note