-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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: if status address already in use, return an error (#15177) #15466
server: if status address already in use, return an error (#15177) #15466
Conversation
Signed-off-by: sre-bot <sre-bot@pingcap.com>
/run-all-tests |
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.
LGTM
/build |
1 similar comment
/build |
@zimulala Please fix the CI |
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.
LGTM
/run-unit-test |
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.
LGTM
/merge |
/run-all-tests |
cherry-pick #15177 to release-3.0
conflicts:
server/http_status.go
server/server.go
server/tidb_test.go
What problem does this PR solve?
If the status address already in use, we only log it. We don't know why the status server is unavailable except by looking at the logs.
If we don't start the status server, we can set
report-status
to false.What is changed and how it works?
If the status address already in use, we return an error and interrupt the service.
Check List
Tests
Related changes
Release note