[ 
https://issues.apache.org/jira/browse/SPARK-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064478#comment-14064478
 ] 

Nicholas Chammas commented on SPARK-2463:
-----------------------------------------

{quote}
Yeah, as a first step, we should detect that some is trying to create/start
another StreamingContext using the same SparkContext, and throw an error.
{quote}

I understand that it is currently not possible to restart a StreamingContext 
once it is stopped. So making such a change as you are describing would mean 
that once you stop your StreamingContext you need to create a new SparkContext 
to get a new StreamingContext. And if you're working in the shell, that means 
you have to quit and restart the shell. Is that correct?

I honestly don't appreciate the level of work being discussed here because I 
know very little about Spark internals, but I can say that form a user 
perspective not being able to easily restart or recreate StreamingContexts 
would be user-unfriendly--especially in the stages of development and iteration 
where you are likely to want to start and stop stream processing over and over 
from the shell.

> Creating multiple StreamingContexts from shell generates duplicate Streaming 
> tabs in UI
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-2463
>                 URL: https://issues.apache.org/jira/browse/SPARK-2463
>             Project: Spark
>          Issue Type: Bug
>          Components: Streaming, Web UI
>    Affects Versions: 1.0.1
>            Reporter: Nicholas Chammas
>
> Start a {{StreamingContext}} from the interactive shell and then stop it. Go 
> to {{http://master_url:4040/streaming/}} and you will see a tab in the UI for 
> Streaming.
> Now from the same shell, create and start a new {{StreamingContext}}. There 
> will now be a duplicate tab for Streaming in the UI. Repeating this process 
> generates additional Streaming tabs. 
> They all link to the same information.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to