-
Notifications
You must be signed in to change notification settings - Fork 605
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
[LIVY-336][SERVER] Livy should not spawn one thread per job to track the job on Yarn #242
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #242 +/- ##
============================================
+ Coverage 68.09% 68.23% +0.14%
- Complexity 939 949 +10
============================================
Files 102 102
Lines 5883 5935 +52
Branches 893 904 +11
============================================
+ Hits 4006 4050 +44
- Misses 1302 1310 +8
Partials 575 575
Continue to review full report at Codecov.
|
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.
Nice PR proposal, it should have been done long time ago) Added some comments. I see that improvements that can be done here with rearranging code a bit. Would you mind if I propose some changes on to your branch?
Suggestions: runzhiwang#1
8839fb4
to
f949f66
Compare
@jahstreet Thank you for your comments. I have updated the PR. |
@runzhiwang Yeah, I see, will go through once again during weekend. Good job man! |
01a445e
to
2b38d51
Compare
I still need a close look to see the detailed implementations. |
I'm OK with the current changes, @yiheng would you please also take a look. |
ce12169
to
61d5d38
Compare
Looks ok from my side, @yiheng please help to review again. |
d5d0b0a
to
9521863
Compare
12ebee8
to
b18fad1
Compare
b18fad1
to
b21e404
Compare
24561ab
to
c3c86e3
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.
Added some comments, other than that looks nice so far, good job!
@jahstreet Thank you very much, I have updated according to your comments. |
@runzhiwang can you test your patch on a Yarn cluster? |
@jahstreet OK. |
@jahstreet Hi, I have test the patch, and it works fine. |
Thread.sleep(yarnPoolInterval) | ||
} catch { | ||
case e: InterruptedException => | ||
loop = false |
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.
Should we keep in the loop? I'm afraid the thread is interrupted while the livy is still running. Then all the app status won't change.
Hey @runzhiwang what's the status of this PR? Are you going to merge this in? I'm having issues with dangling threads with a lot of jobs running simultaneously and this fix will be great to have! |
@sanchay0 Thanks for your attention. I have completed the code. And It just need more review. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #242 +/- ##
=========================================
Coverage 68.23% 68.23%
- Complexity 941 949 +8
=========================================
Files 102 102
Lines 5883 5935 +52
Branches 893 904 +11
=========================================
+ Hits 4014 4050 +36
- Misses 1295 1310 +15
- Partials 574 575 +1 ☔ View full report in Codecov by Sentry. |
What changes were proposed in this pull request?
Instead of spawning a monitor thread for every session, create a centralized thread to monitor all apps.
How was this patch tested?
Existed ITs and UTs.