-
Notifications
You must be signed in to change notification settings - Fork 97
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
Added logic for single node restoration after abrupt shutdown. #482
Conversation
545d6d3
to
7fe6ca2
Compare
/assign |
This PR adds support for single node restoration only from revision mismatches and not from data/PV corruption |
Yes. Only that. |
7fe6ca2
to
fc77b33
Compare
fc77b33
to
2df0c3a
Compare
In CI pipeline Integration tests again went into this issue #483 |
/retest |
2df0c3a
to
8907ca1
Compare
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.
From what I can tell it looks good. Can you double check the test or re-run them please?
Do not merge this PR. I have some doubts. |
8907ca1
to
d79a491
Compare
Addresses #489 |
What this PR does / why we need it:
If a node abruptly shutdown in ETCD multi node cluster, it checks revision before coming back up. If the revision number is lesser than the latest snapshot, it fails to restore. Whereas this check is necessary for a single node cluster, it's not necessary for a multinode setup. This PR takes care of both type of clusters.
Which issue(s) this PR fixes:
Fixes #481
Special notes for your reviewer:
Release note: