Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.apache.org
Date: Sat, 7 Jun 2014 12:06:01 +0000 (UTC)
From: "Mridul Muralidharan (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12718957.1402094738306.87232.1402142761458@arcas>
In-Reply-To: <JIRA.12718957.1402094738306@arcas>
References: <JIRA.12718957.1402094738306@arcas>
Subject: [jira] [Commented] (SPARK-2064) web ui should not remove executors
 if they are dead
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mridul Muralidharan commented on SPARK-2064:
--------------------------------------------

Depending on how long a job runs, this can cause OOM on the master.
In yarn (and mesos ?) an executor on the same node gets different port if relaunched on failure - and so end up as different executor in the list.

> web ui should not remove executors if they are dead
> ---------------------------------------------------
>
>                 Key: SPARK-2064
>                 URL: https://issues.apache.org/jira/browse/SPARK-2064
>             Project: Spark
>          Issue Type: Sub-task
>            Reporter: Reynold Xin
>
> We should always show the list of executors that have ever been connected, and add a status column to mark them as dead if they have been disconnected.


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