PoC recovering reconcile panics as errors #5992
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've encountered two recent virt-controller crashes (#5849 and #5694) that were caused by resources entering into unexpected states. The result is that a crash in one of our reconcile loops crashes all of virt-controller, which can cause the entire virt-controller process to enter into a crash loop.
Using the built in golang
recover()
function, we can catch and handle panics that occur during our reconcile loops and simply treat them as errors which then get rate limited.This PR exists to illustrate how this can be done for the sake of discussion.