-
Notifications
You must be signed in to change notification settings - Fork 324
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
HEP: System robustness enhancement [CI SKIP] #4464
Conversation
BTW: all review comments are welcome, thanks. |
Brainstorming:
oversimplifying a bit - but might be a good start. |
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions. |
reopening, this is still meant to be active |
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions. |
ping, keeping this PR active |
2edb2d8
to
b572ecf
Compare
0cbc671
to
f0e4c19
Compare
f0e4c19
to
5f61148
Compare
5f61148
to
a4ce171
Compare
Signed-off-by: Jian Wang <w13915984028@gmail.com>
a4ce171
to
417806f
Compare
This repository uses an automated workflow to automatically label pull requests which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community pull requests better. If the pull request is still relevant, please add a comment to the pull request so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the pull request in 14 days. Thank you for your contributions. |
IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:
How to gracefully shutdown an running Harvester cluster? no clear answer yet.
Solution:
Add to a new feature to accomplish this.
Related Issue:
#3261
One previous DOC PR: docs: add cluster shutdown and restart
Test plan: