[
https://issues.apache.org/jira/browse/SPARK-16539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-16539.
----------------------------------
Resolution: Incomplete
> When worker is killed driver continues to run causing issues in supervise mode
> ------------------------------------------------------------------------------
>
> Key: SPARK-16539
> URL: https://issues.apache.org/jira/browse/SPARK-16539
> Project: Spark
> Issue Type: Bug
> Components: Scheduler, Spark Core
> Affects Versions: 1.6.1
> Environment: Ubuntu 14.04
> Reporter: Noorul Islam K M
> Priority: Major
> Labels: bulk-closed, supervise
>
> Spark version: 1.6.1
> Cluster Manager: Standalone
> I am experimenting with cluster mode deployment along with supervise for
> high availability of streaming applications.
> 1. Submit a streaming job in cluster mode with supervise
> 2. Say that driver is scheduled on worker1. The app started
> successfully.
> 3. Kill worker1 java process. This does not kill driver process and
> hence the application (context) is still alive.
> 4. Because of supervise flag, driver gets scheduled to new worker
> worker2 and hence a new context is created, making it a duplicate.
> I think this seems to be a bug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
