[#1211] fix: Unexpectedly removing resources even though the App has re-registered shuffle later. - #1212
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1212 +/- ##
============================================
+ Coverage 53.68% 54.88% +1.20%
- Complexity 2588 2604 +16
============================================
Files 391 372 -19
Lines 22425 20135 -2290
Branches 1875 1886 +11
============================================
- Hits 12038 11051 -987
+ Misses 9682 8447 -1235
+ Partials 705 637 -68
... and 25 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
@zuston Could you review code for me if you are available? Thanks! |
zuston
left a comment
There was a problem hiding this comment.
isAppExpired looks good to me. But I don't get the point about the appLocks .
|
@zuston As we discussed before, we cannot predict the execution order of
Please correct me if I'm wrong or you can provide better suggestions. Thanks! |
|
This seems to have broken things for me. The call to the guava cache throws an execption in the shuffle server: Reverting the commit fixes the issue |
…registered shuffle later (#1212) ### What changes were proposed in this pull request? 1. check again if the App has expired when removing resources. 2. add the lock of app scope to keep the sequence of remove and register operations ### Why are the changes needed? Fix: #1211 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Add more tests.
What changes were proposed in this pull request?
Check again if the App has expired when removing resources.
Why are the changes needed?
Fix: #1211
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add more tests.