-
Notifications
You must be signed in to change notification settings - Fork 0
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
[PE-1779] add retry in case of inserter failure #28
[PE-1779] add retry in case of inserter failure #28
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #28 +/- ##
=======================================
Coverage 70.97% 70.97%
=======================================
Files 15 15
Lines 1664 1664
=======================================
Hits 1181 1181
Misses 346 346
Partials 137 137 ☔ View full report in Codecov by Sentry. |
f882e13
to
4ecf612
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.
I am not familiar with this retry mechanism, so I might be wrong on my assumptions, but, from what I noticed:
- There is no limit on how many retries
- There is no indication or log something happened
- There is no validation for the type of error (should we retry if context canceled?)
This means if something is wrong, this will go to endless loop without any indication to the caller.
I think its better to move the retry mechanism to the inserter/agent and not to implement it on the KV level.
thoughts?
I am usually using this library: https://pkg.go.dev/github.com/avast/retry-go
I prefer to use k8s retry and not an external library |
4ecf612
to
2b17ad2
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.
few nits
2b17ad2
to
423b399
Compare
Add retry for k8s calls in inserter