logutil: force level of slow logger to "debug"#28688
logutil: force level of slow logger to "debug"#28688SabaPing wants to merge 4 commits intopingcap:masterfrom
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
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. DetailsReviewer can indicate their review by submitting an approval review. |
|
Please fill the release note, and pick up suitable release versions. |
|
@SabaPing PTAL |
I will back to this issue late afternoon today. |
|
@SabaPing Do you have updates~? |
Ahhh, I spent more time than expected on development yesterday, and I also handled a few oncalls on cloud in the afternoon, so I really didn't have time. I hope I can handle this issue this afternoon. |
|
Manual test steps:
|
|
Fixed in #30461. |
What problem does this PR solve?
Fix oncall issue https://internal.pingcap.net/jira/browse/ONCALL-3746.
Setting TiDB's
log.leveltoerrorcauses that the slow log does not print.One must set the
log.leveltoinfoorwarnvia tiup cluster edit-config and reload the TiDB node to re-enable the slow logs.This PR fix this issue. After fixing, global
log.levelshould not affects slow logs.Manual test steps
Start TiDB with command line arguement -L=error.
Slow logs should output normally.
Release note