Skip to content
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

[logutil]: Fix MaxDays and MaxBackups not working for slow-query-logger #27625

Merged
merged 8 commits into from
Nov 18, 2021

Conversation

SabaPing
Copy link
Contributor

@SabaPing SabaPing commented Aug 27, 2021

What problem does this PR solve?

Fix MaxDays and MaxBackups not working for slow-query-logger

Issue Number: #25716

Problem Summary:

MaxDays and MaxBackups not working for slow-query-logger. This may causes unexpected disk usage.

What is changed and how it works?

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Manual test steps

Test MaxDays:

  1. Create a directory named slowlog.
  2. Create a file named slowlog-2021-11-01T23-00-00.001
  3. Start TiDB with following config:
    [log.file]
    max-days = 1
    enable-slow-log = true
    slow-query-file = "PATH_TO_SLOWLOG_DIRECTORY/slowlog"
  4. One should observe previously created file slowlog-2021-11-01T23-00-00.001 got deleted.

Test MaxBackups:

  1. Create a directory named slowlog.
  2. Create two files named slowlog-2021-11-01T23-00-00.001 and slowlog-2021-11-02T23-00-00.001.
  3. Start TiDB with following config:
    [log.file]
    max-backups = 1
    enable-slow-log = true
    slow-query-file = "PATH_TO_SLOWLOG_DIRECTORY/slowlog"
  4. One should observe previously created file slowlog-2021-11-01T23-00-00.001 got deleted.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Fix `MaxDays` and `MaxBackups` not working for slow log.

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Aug 27, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • qw4990
  • wjhuang2016

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 27, 2021
@crazycs520
Copy link
Contributor

@bb7133 PTAL

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Aug 31, 2021
@SabaPing
Copy link
Contributor Author

/run-check_dev_2

@bb7133
Copy link
Member

bb7133 commented Nov 11, 2021

Hi @SabaPing did you verified the change locally?

@bb7133
Copy link
Member

bb7133 commented Nov 11, 2021

Please provide a 'manual test' in the PR description, thanks!

@jyz0309
Copy link
Contributor

jyz0309 commented Nov 17, 2021

/run-check_dev_2

@jyz0309
Copy link
Contributor

jyz0309 commented Nov 17, 2021

I have tested it, /cc @bb7133

@jyz0309
Copy link
Contributor

jyz0309 commented Nov 17, 2021

/run-check_dev_2

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Nov 18, 2021
@wjhuang2016
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 9667580

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Nov 18, 2021
@jyz0309
Copy link
Contributor

jyz0309 commented Nov 18, 2021

/run-check_dev_2

@ti-chi-bot ti-chi-bot merged commit 46de14d into pingcap:master Nov 18, 2021
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Nov 18, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.2 in PR #29921

@YuJuncen
Copy link
Contributor

/run-cherry-picker

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Nov 26, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.1 in PR #30171

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Nov 26, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.3 in PR #30172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-5.1 needs-cherry-pick-release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants