ttl: refactor TTL to seperate creating new job and take timeout job codes

[lcwangchao]

What problem does this PR solve?

Issue Number: close #45285

There are two scenes for a tidb instance to lock and execute a job:

1. A table is time to execute, a new job should be created.
2. A exist job's heartbeat is timeout, the tidb should take over it.

In the previous implement this two scenes and processed in one method and not separated. However, in the future we want to move the trigger codes to timer so it's better to separate the above code from two scenes apart.

What is changed and how it works?

Refactor method lockNewJob to lockJob and it can pass the extra argument isCreate, if isCreate is true, it only creates a new job and if isCreate is false, it only takes over the timeout job.

Check List

Tests

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

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[hawkingrei]

/test tiprow_fast_test

[ti-chi-bot]

@hawkingrei: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-e2e-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test unit-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test tiprow_fast_test

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 kubernetes/test-infra repository.

[YangKeao]

LGTM

[hawkingrei]

/test tiprow_fast_test

[ti-chi-bot]

@hawkingrei: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-e2e-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test unit-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test tiprow_fast_test

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 kubernetes/test-infra repository.

[lcwangchao]

/retest

[lcwangchao]

/test tiprow_fast_test

[ti-chi-bot]

@lcwangchao: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-e2e-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test unit-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test tiprow_fast_test

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 kubernetes/test-infra repository.

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[lcwangchao]

/retest

[bb7133]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, YangKeao

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [YangKeao,bb7133]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-07-11 06:45:35.975217848 +0000 UTC m=+400827.745556548: ☑️ agreed by YangKeao.
• 2023-07-13 06:00:52.654104231 +0000 UTC m=+570944.424442943: ☑️ agreed by bb7133.

[bb7133]

/merge

[ti-chi-bot]

@bb7133: We have migrated to builtin LGTM and approve plugins for reviewing.

Please use /approve when you want approve this pull request.

The changes announcement: LGTM plugin changes

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.

[tiprow]

@lcwangchao: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tiprow_fast_test	17190ccef3ec24a7b1b1ed081c400b0cfa7b13e2	link	true	/test tiprow_fast_test

Full PR test history. Your PR dashboard.

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 kubernetes/test-infra repository. I understand the commands that are listed here.