-
Notifications
You must be signed in to change notification settings - Fork 27
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
🐛Clusters-keeper: calling >100 times for the same new cluster now returns cached information #5201
🐛Clusters-keeper: calling >100 times for the same new cluster now returns cached information #5201
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #5201 +/- ##
========================================
- Coverage 89.4% 86.9% -2.5%
========================================
Files 1121 1031 -90
Lines 45899 44422 -1477
Branches 1057 603 -454
========================================
- Hits 41049 38631 -2418
- Misses 4619 5650 +1031
+ Partials 231 141 -90
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Cool! Thanks a lot.
Looks good to me
52048d6
to
0495f0d
Compare
5cd3b46
to
c1f8620
Compare
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
What do these changes do?
when running many jobs through the public API, we actually create as many projects as jobs for 1 same user.
When starting them all at the same time, we actually need to get_or_create the very same cluster at the same time which means there are as many very same call to the clusters-keeper via RPC, then locking a distributed lock, then calling into AWS.
This PR ensures that:
In effect, this prevents calls from going more often than once every 5 seconds for the same user_id/wallet_id combination
Related issue/s
How to test
Dev Checklist
DevOps Checklist