-
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
Decouple the readinessProbe of etcd and Snapshotter #411
Decouple the readinessProbe of etcd and Snapshotter #411
Conversation
c211158
to
a8897eb
Compare
a8897eb
to
0cf0109
Compare
0cf0109
to
d4abe00
Compare
d4abe00
to
a0c0201
Compare
a0c0201
to
361829e
Compare
361829e
to
a722611
Compare
Hi @shreyas-s-rao, |
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.
@ishan16696 Thanks for making the changes! Except for one small nitpick, LGTM 👍🏼
Added a BackoffExponential mechanism for Snapshotter failure.
e1010fd
to
1de781c
Compare
1de781c
to
82656d3
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.
Thanks. Looks good.
What this PR does / why we need it:
Currently, snapshotter fails the readiness probe of etcd if it fails to take/upload the backup, thus cutting off incoming traffic to etcd until snapshotter becomes healthy again.
This PR decouples the readinessProbe of etcd and snapshotter health of backup-restore.So, Backup-restore's snapshotter failure won't fails the readinessProbe of etcd and hence etcd will allow to keep serving the incoming traffic.
This PR also introduced a Exponential-Backoff mechanism in Snapshotter(if Snapshotter fails.)
Which issue(s) this PR fixes:
Fixes #325
Special notes for your reviewer:
Release note: