br: use the correct unit for pausing schedulers (#33545)

[ti-srebot]

cherry-pick #33545 to release-5.2
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/33813

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/33813:release-5.2-53042e7aab60

---

Signed-off-by: Ryan Leung rleungx@gmail.com

What problem does this PR solve?

Issue Number: close #33546.

Problem Summary: The unit for TTL of schedulers is not correct. We should use second as the unit.

What is changed and how it works?

Check List

Tests

• Manual test

1. start a cluster with TiUP
2. use lightning to import data
3. kill lightning with kill -9

Here is the log of PD:

[2022/03/29 14:26:07.097 +08:00] [INFO] [handler.go:272] ["pause scheduler successfully"] [scheduler-name=balance-region-scheduler] [pause-seconds=300]
[2022/03/29 14:26:07.097 +08:00] [INFO] [handler.go:272] ["pause scheduler successfully"] [scheduler-name=balance-leader-scheduler] [pause-seconds=300]
[2022/03/29 14:26:07.098 +08:00] [INFO] [handler.go:272] ["pause scheduler successfully"] [scheduler-name=balance-hot-region-scheduler] [pause-seconds=300]

Release note

Fix the issue that the schedulers won't be resumed after BR/Lightning exits abnormally.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• JmPotato
• glorv

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-srebot]

/run-all-tests

[ti-srebot]

@rleungx you're already a collaborator in bot's repo.

[glorv]

@3pointer @YuJuncen PTAL at the CI failure:

[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-2)[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-3)[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-4)[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-5)[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-6)[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-7)[](https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/44253/pipeline#step-73-log-8)[2022-04-08T06:40:15.942Z] + ulimit -c unlimited

[2022-04-08T06:40:15.942Z] + export GOBACTRACE=crash

[2022-04-08T06:40:15.942Z] + GOBACTRACE=crash

[2022-04-08T06:40:15.942Z] + export log_level=warn

[2022-04-08T06:40:15.942Z] + log_level=warn

[2022-04-08T06:40:15.942Z] + make br_unit_test_in_verify_ci

[2022-04-08T06:40:15.942Z] make: *** No rule to make target `br_unit_test_in_verify_ci'.  Stop.

No test report files were found. Configuration error?

[VelocityLight]

This pull request is closed because it's related version has closed automatic cherry-picking.
If it's still needed, you can reopen it or just regenerate it using bot,
see:

• https://prow.tidb.io/command-help#cherrypick
• https://book.prow.tidb.net/#/plugins/cherrypicker

You can find more details at:

• https://internals.tidb.io/t/topic/785