-
Notifications
You must be signed in to change notification settings - Fork 355
fix: attempt to shut down when provider init fails #2263
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
fix: attempt to shut down when provider init fails #2263
Conversation
This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the [email protected] list. Thank you for your contributions. |
would be great if a maintainer could look at this eventually |
@Revolyssup sorry about the direct ping, are you still working on the ingress or could you direct me to someone who can help? |
Hey @AlinsRan, could you please take a look at this when you have a chance? Your review would help us keep things moving. Thanks a lot! |
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 a lot
Fixes #1980.
Simpler version of #2152 that shouldn't break any tests, since it doesn't touch leader election.
Also addresses #2236.
This one just adds communicating failure from
run
back toRun
, tried to shut down gracefully, but forces a shutdown after 5 seconds.Still wouldn't recommend running two replicas, the code has some potential races.