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

ERROR 1231 (42000): Variable 'tidb_gc_life_time' can't be set to the value of '72h0m0s' #35392

Closed
asddongmen opened this issue Jun 15, 2022 · 4 comments · Fixed by #35411
Closed
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@asddongmen
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. tiup playground v6.1.0
  2. use mysql client to connect to tidb server
  3. SET GLOBAL TIDB_GC_LIFE_TIME= '72h';
  4. ERROR 1231 (42000): Variable 'tidb_gc_life_time' can't be set to the value of '72h0m0s'

2. What did you expect to see? (Required)

Query OK

3. What did you see instead (Required)

ERROR 1231 (42000): Variable 'tidb_gc_life_time' can't be set to the value of '72h0m0s'

4. What is your TiDB version? (Required)

+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v6.1.0
Edition: Community
Git Commit Hash: 1a89decdb192cbdce6a7b0020d71128bc964d30f
Git Branch: heads/refs/tags/v6.1.0
UTC Build Time: 2022-06-05 05:09:33
GoVersion: go1.18.2
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@TonsnakeLin
Copy link
Contributor

/label affect-6.1

@ti-chi-bot
Copy link
Member

@TonsnakeLin: The label(s) affect-6.1 cannot be applied. These labels are supported: challenge-program, compatibility-breaker, first-time-contributor, contribution, require-LGT3, good first issue, correctness, duplicate, proposal, security, needs-more-info, needs-cherry-pick-4.0, needs-cherry-pick-5.0, needs-cherry-pick-5.1, needs-cherry-pick-5.2, needs-cherry-pick-5.3, needs-cherry-pick-5.4, needs-cherry-pick-6.0, needs-cherry-pick-6.1, affects-4.0, affects-5.0, affects-5.1, affects-5.2, affects-5.3, affects-5.4, affects-6.0, affects-6.1, may-affects-4.0, may-affects-5.0, may-affects-5.1, may-affects-5.2, may-affects-5.3, may-affects-5.4, may-affects-6.0, may-affects-6.1.

In response to this:

/label affect-6.1

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 ti-community-infra/tichi repository.

@TonsnakeLin
Copy link
Contributor

/label affects-6.1

@ti-chi-bot ti-chi-bot added the affects-6.1 This bug affects the 6.1.x(LTS) versions. label Jun 16, 2022
@TonsnakeLin
Copy link
Contributor

/label needs-cherry-pick-6.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants