-
Notifications
You must be signed in to change notification settings - Fork 282
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
p2p(ticdc): add keep alive configuration for p2p server (#8908) #8939
p2p(ticdc): add keep alive configuration for p2p server (#8908) #8939
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3AceShowHand, sdojjy 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:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest-required |
1 similar comment
/retest-required |
/retest |
This is an automated cherry-pick of #8908
What problem does this PR solve?
Issue Number: close #8907
What is changed and how it works?
if a ticdc server is hang (kill -19), the owner can not send a heartbeat message to the processor, which will cause the changefeed has a 2hours LAG(the default grpc keep alive time)
this pr adds keep alive configuration for p2p server
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note