-
Notifications
You must be signed in to change notification settings - Fork 499
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
Before proceeding to initialize TiDB, we wait for the TiDB host:port is open. #1296
Conversation
/run-e2e-test |
- sh | ||
- -c | ||
- | | ||
trap exit TERM |
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.
able to terminate fast on kill container signal (TERMINAL) (xref: kubernetes/kubernetes#64015 (comment))
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.
I always run something like dumb-init in my pods so that these issues don't show up
…nto wait-on-tidb-ready
/run-e2e-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
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
What problem does this PR solve?
#1255
What is changed and how does it work?
Before proceeding to initialize TiDB, we wait for the TiDB
host:port
is open. This avoids unnecessary pod restarts which may result in a very long restart delay (10s, 20s, .., 5 mins).https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy
Check List
Tests
Does this PR introduce a user-facing change?: