spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Davidson (JIRA)" <>
Subject [jira] [Reopened] (SPARK-1689) AppClient does not respond correctly to RemoveApplication
Date Tue, 20 May 2014 02:04:37 GMT


Aaron Davidson reopened SPARK-1689:

The new behavior correctly informs the scheduler of the failed state, but does not exit though
we've been removed.

Created to fix this issue.

> AppClient does not respond correctly to RemoveApplication
> ---------------------------------------------------------
>                 Key: SPARK-1689
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 0.9.0, 1.0.0
>            Reporter: Aaron Davidson
>            Assignee: Aaron Davidson
>             Fix For: 1.0.0
> When the Master removes an application (usually due to too many executor failures), it
means no future executors will be assigned to that app. Currently, the AppClient just marks
the application as "disconnected", which is intended as a transient state during a period
of reconnection. Thus, RemoveApplication just causes the application to enter a state where
it has no executors and it doesn't die.

This message was sent by Atlassian JIRA

View raw message