*: Add abort-on-panic config (#10164)

[ti-srebot]

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

# In tikv repo:
git pr https://github.com/tikv/tikv/pull/10216

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

git push [email protected]:ti-srebot/tikv.git pr/10216:release-5.0-421e6e068c20

---

Signed-off-by: Yi Wu [email protected]

What problem does this PR solve?

Problem Summary:

• Add a config abort-on-panic to allow TiKV generate a core dump. This is useful when core dump is desire to investigate issues.
• Adding message in panic_mark_file fatal log to warn users not to delete the panic_mark_file and force restart.
• Adding a warning when tikv-ctl encounter rocksdb LOCK file conflict, which warns user not to delete the LOCK file.

What is changed and how it works?

What's Changed: Add the above two configs.

Related changes

• PR to update pingcap/docs/pingcap/docs-cn: will send PR later.
• Need to cherry-pick to the release branch: release-5.0

Check List

Tests
Manually test the flows

Release note

• Add abort-on-panic config, which allow core dump to be generated when panic. Users still need to correctly config the environment to enable core dump.

[ti-srebot]

/run-all-tests

[ti-srebot]

@yiwu-arbug you're already a collaborator in bot's repo.

[yiwu-arbug]

/test

[Connor1996]

LGTM

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Connor1996
• yiwu-arbug

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[yiwu-arbug]

/merge

[ti-chi-bot]

@yiwu-arbug: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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.

[ti-chi-bot]

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

Commit hash: fca113b

[ti-chi-bot]

@ti-srebot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

[yiwu-arbug]

/merge

[ti-chi-bot]

@yiwu-arbug: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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.