[
https://issues.apache.org/jira/browse/SPARK-17707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548913#comment-15548913
]
Sean Owen commented on SPARK-17707:
-----------------------------------
Ah, yes you do need to call stop() at the end of your app. That could be why
I'm not seeing this.
There is one non-daemon thread:
{code}
"Scheduler-23010977" #182 prio=5 os_prio=0 tid=0x00007f6c70001800 nid=0x620c
waiting on condition [0x00007f6dc4be9000]
{code}
I admit, I am not sure if this is a Spark thread, though I assume it is; I
can't find something that makes threads with this name. If we can track that
down maybe it could be made a daemon. In any event that's the cause, although,
calling stop() in a finally block at the top level of the program may be the
right thing to do in any event.
> Web UI prevents spark-submit application to be finished
> -------------------------------------------------------
>
> Key: SPARK-17707
> URL: https://issues.apache.org/jira/browse/SPARK-17707
> Project: Spark
> Issue Type: Bug
> Affects Versions: 2.0.0, 2.0.1
> Reporter: Nick Orka
>
> Here are re-production steps:
> 1. create any scala spark application which will work long enough to open the
> application details in Web UI
> 2. run spark-submit command for standalone cluster, like: --master
> spark:\\localhost:7077
> 3. open running application details in Web UI, like: localhost:4040
> 4. spark-submit will never finish, you will have to kill the process
> Cause: The application creates a thread with infinite loop for web UI
> communication and never stops it. The application is waiting for the thread
> to be finished instead, even if you close the web page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
