[
https://issues.apache.org/jira/browse/SPARK-17707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548952#comment-15548952
]
Sean Owen commented on SPARK-17707:
-----------------------------------
OK so it's pretty clear the "Scheduler-x" thread is somehow started only when
the UI is touched. maybe it's from inside Jetty.
I don't know why it might have happened to work before, but in general I'd
expect that an app that has long-running threads has to shut itself down
explicitly.
If there's an easy way to make this a daemon thread, OK, seems worth changing
that, but stop() is still the intended way to close the app correctly.
> 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]
