kv/client: support reconnect regions when no event received too long (#1591,#1674,#1686)

[ti-srebot]

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

# In ticdc repo:
git pr https://github.com/pingcap/ticdc/pull/1668

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

git push [email protected]:ti-srebot/ticdc.git pr/1668:release-4.0-fd90b40f37e4

---

What problem does this PR solve?

Solve https://github.com/pingcap/ticdc/issues/1586 (This is the master PR, release-5.0 PR is https://github.com/pingcap/ticdc/pull/1589)

NOTE, need discussion:

1. The check only workers after region is initialized, is this reasonable.
2. The reconnect interval (15m) is hard coded, we need to discuss whether to add a config in server config file

After discussion

1. Keep check after the region is initialized, because the incremental scan phase could cost long.
2. We don't need to add it in server config file, since the check is only in real time data phase.

What is changed and how it works?

• Reuse kv event aliveness check in lock resolver tick
• If a region doesn't receive any event for more than 15 minutes, force the gRPC stream to reconnect
• Only update the kv client v1, kv client v2 will be updated later

Check List

Tests

• Unit test
• Integration test

Release note

• Force the gRPC stream to reconnect if no event (including resolved ts event) is received for more than 15 minutes.

[ti-srebot]

/run-all-tests

[sre-bot]

No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md

[amyangfei]

/run-all-tests

[amyangfei]

/run-all-tests

[amyangfei]

/run-all-tests

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (release-4.0-pending@6602c6a). Click here to learn what that means.
The diff coverage is n/a.

@@                   Coverage Diff                    @@
##             release-4.0-pending      #1668   +/-   ##
========================================================
  Coverage                       ?   50.6473%           
========================================================
  Files                          ?        152           
  Lines                          ?      15835           
  Branches                       ?          0           
========================================================
  Hits                           ?       8020           
  Misses                         ?       6978           
  Partials                       ?        837           

[zier-one]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• amyangfei
• leoppro

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.

[ti-chi-bot]

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

Commit hash: f9c5cf9

[amyangfei]

/run-all-tests

[amyangfei]

/run-kafka-tests

[amyangfei]

/merge

[ti-chi-bot]

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

Commit hash: f3db866

[amyangfei]

cherry-pick #1674 together, close #1679

[amyangfei]

/run-unit-tests

[amyangfei]

/run-integration-tests

[amyangfei]

/run-all-tests

[amyangfei]

/run-kafka-tests

[amyangfei]

/merge

[ti-chi-bot]

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

Commit hash: 53bb12c

[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.

[amyangfei]

/run-all-tests

[amyangfei]

/run-leak-tests