-
Notifications
You must be signed in to change notification settings - Fork 247
chore: support fixed requeue rate for pod not-found error #9961
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
chore: support fixed requeue rate for pod not-found error #9961
Conversation
|
Auto Cherry-pick Instructions |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9961 +/- ##
==========================================
+ Coverage 51.02% 51.16% +0.13%
==========================================
Files 541 541
Lines 58346 58350 +4
==========================================
+ Hits 29771 29852 +81
+ Misses 25632 25565 -67
+ Partials 2943 2933 -10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/cherry-pick release-0.9 |
|
/cherry-pick release-1.0 |
|
🤖 says: cherry pick action finished successfully 🎉! |
(cherry picked from commit 201d60b)
|
🤖 says: cherry pick action finished successfully 🎉! |
(cherry picked from commit 201d60b)
pod not founderror happens because of pod role restoring after mongodb restore action complete. Role resotring only takes several seconds. But controller-runtime's default exponential rate limiter makeerror -> requeue->reconciletime longer and longer. It might take 3 minutes for restore cr complete after restore action complete.