-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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
[SPARK-32598][Scheduler] Fix missing driver logs under UI App-Executors tab in standalone cluster mode #29644
Conversation
1c396c7
to
0b4218d
Compare
@srowen Can you also help find someone review this PR? Thanks! |
In standalone mode aren't these just the logs from the application driver, the stdout output? I don't know this part well (and not enough to review) |
Yes, it's just stdout & stderr of driver, currently missing in web-ui. Thanks anyway! @srowen |
219e16b
to
6dcdcdf
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.
IIUC, this only works for the cluster mode? If so, we could set the driver log URLs through the env variable in DriverRunner
like ExecutorRunner
does? Then, we can avoid RPC calls between driver and Master.
9f85ba3
to
2188497
Compare
@Ngone51 Thanks for your suggestion! Yes you're right, I have updated this patch. I was thinking of using RPC to get full worker info may help further changes, seems no need. |
2188497
to
b6f08a0
Compare
core/src/main/scala/org/apache/spark/scheduler/cluster/StandaloneSchedulerBackend.scala
Outdated
Show resolved
Hide resolved
core/src/test/scala/org/apache/spark/status/AppStatusListenerSuite.scala
Outdated
Show resolved
Hide resolved
b6f08a0
to
60764a6
Compare
core/src/main/scala/org/apache/spark/scheduler/cluster/StandaloneSchedulerBackend.scala
Outdated
Show resolved
Hide resolved
Can you do some manual tests and paste screenshots of UI to show the fix result in the PR description? |
60764a6
to
a0bdce9
Compare
Done |
LGTM. I also verified locally. It looks good. @jiangxb1987 Could you also take a look? |
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.
LGTM
@HyukjinKwon Can you help let Jenkins test this? |
retest this please |
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #129656 has finished for PR 29644 at commit
|
Test build #134103 has finished for PR 29644 at commit
|
…rs tab in standalone cluster mode ### What changes were proposed in this pull request? Fix [SPARK-32598] (missing driver logs under UI-ApplicationDetails-Executors tab in standalone cluster mode) . The direct bug is: the original author forgot to implement `getDriverLogUrls` in `StandaloneSchedulerBackend` https://github.com/apache/spark/blob/1de272f98d0ff22d0dd151797f22b8faf310963a/core/src/main/scala/org/apache/spark/scheduler/SchedulerBackend.scala#L70-L75 So we set DriverLogUrls as env in `DriverRunner`, and retrieve it at `StandaloneSchedulerBackend`. ### Why are the changes needed? Fix bug [SPARK-32598]. ### Does this PR introduce _any_ user-facing change? Yes. User will see driver logs (standalone cluster mode) under UI-ApplicationDetails-Executors tab now. Before: ![image](https://user-images.githubusercontent.com/17903517/93901055-b5de8600-fd28-11ea-879a-d97e6f70cc6e.png) After: ![image](https://user-images.githubusercontent.com/17903517/93901080-baa33a00-fd28-11ea-8895-3787c5efbf88.png) ### How was this patch tested? Re-check the real case in [SPARK-32598] and found this user-facing bug fixed. Closes #29644 from KevinSmile/kw-dev-master. Authored-by: KevinSmile <kevinwang013@hotmail.com> Signed-off-by: Sean Owen <srowen@gmail.com> (cherry picked from commit c75c29d) Signed-off-by: Sean Owen <srowen@gmail.com>
…rs tab in standalone cluster mode ### What changes were proposed in this pull request? Fix [SPARK-32598] (missing driver logs under UI-ApplicationDetails-Executors tab in standalone cluster mode) . The direct bug is: the original author forgot to implement `getDriverLogUrls` in `StandaloneSchedulerBackend` https://github.com/apache/spark/blob/1de272f98d0ff22d0dd151797f22b8faf310963a/core/src/main/scala/org/apache/spark/scheduler/SchedulerBackend.scala#L70-L75 So we set DriverLogUrls as env in `DriverRunner`, and retrieve it at `StandaloneSchedulerBackend`. ### Why are the changes needed? Fix bug [SPARK-32598]. ### Does this PR introduce _any_ user-facing change? Yes. User will see driver logs (standalone cluster mode) under UI-ApplicationDetails-Executors tab now. Before: ![image](https://user-images.githubusercontent.com/17903517/93901055-b5de8600-fd28-11ea-879a-d97e6f70cc6e.png) After: ![image](https://user-images.githubusercontent.com/17903517/93901080-baa33a00-fd28-11ea-8895-3787c5efbf88.png) ### How was this patch tested? Re-check the real case in [SPARK-32598] and found this user-facing bug fixed. Closes #29644 from KevinSmile/kw-dev-master. Authored-by: KevinSmile <kevinwang013@hotmail.com> Signed-off-by: Sean Owen <srowen@gmail.com> (cherry picked from commit c75c29d) Signed-off-by: Sean Owen <srowen@gmail.com>
Merged to master/3.1/3.0. It conflicted in 2.4; if we need it there, it needs another PR. |
What changes were proposed in this pull request?
Fix [SPARK-32598] (missing driver logs under UI-ApplicationDetails-Executors tab in standalone cluster mode) .
The direct bug is: the original author forgot to implement
getDriverLogUrls
inStandaloneSchedulerBackend
spark/core/src/main/scala/org/apache/spark/scheduler/SchedulerBackend.scala
Lines 70 to 75 in 1de272f
So we set DriverLogUrls as env in
DriverRunner
, and retrieve it atStandaloneSchedulerBackend
.Why are the changes needed?
Fix bug [SPARK-32598].
Does this PR introduce any user-facing change?
Yes. User will see driver logs (standalone cluster mode) under UI-ApplicationDetails-Executors tab now.
Before:
After:
How was this patch tested?
Re-check the real case in [SPARK-32598] and found this user-facing bug fixed.