-
Notifications
You must be signed in to change notification settings - Fork 600
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
feat: apply retry strategy when recovery #1768
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1768 +/- ##
==========================================
- Coverage 71.17% 71.15% -0.02%
==========================================
Files 601 601
Lines 77937 77950 +13
==========================================
- Hits 55469 55468 -1
- Misses 22468 22482 +14
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
loop { | ||
tokio::time::sleep(Self::RECOVERY_RETRY_INTERVAL).await; | ||
|
||
let retry_category = Self::get_retry_strategy(); |
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.
let retry_category = Self::get_retry_strategy(); | |
let retry_strategy = Self::get_retry_strategy(); |
Not noticed that the auto-merging is on. 😢 |
My bad, will fix this in another PR. 😁 |
What's changed and what's your intention?
As title, using retry strategy for operation in recovery rather than simple loop and add retry interval for
reset_compute_nodes
.Checklist
Refer to a related PR or issue link (optional)