-
Notifications
You must be signed in to change notification settings - Fork 281
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
server (ticdc): add timeout for statusServer. #5332
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest LGTM
/integration-tests |
/run-integration-tests |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 5cae31f
|
/run-verify |
4 similar comments
/run-verify |
/run-verify |
/run-verify |
/run-verify |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #5346. |
In response to a cherrypick label: new pull request created: #5347. |
What problem does this PR solve?
Issue Number: close #5303
What is changed and how it works?
Invesgation Result:
http.server
connection that cannot be closed and keeps goroutine growing.adminClient
is not closed properly whenNewKafkaSaramaSink
is failed, which can lead to goruotine leaks.Waht is changed:
ReadTimeout
andWriteTimeout
forstatusServer
to limit a connection maxmum alive time.maxConnection
forlistener
ofstatusServer
to limit the maxmum concurrent connections.adminClient
whenNewKafkaSaramaSink
return with error to avoid goroutine leaks.Check List
Tests
Code changes
Side effects
Related changes
Release note