Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Wed, 24 Sep 2014 23:55:33 +0000 (UTC)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12743897.1411602931000.117116.1411602933834@Atlassian.JIRA>
In-Reply-To: <JIRA.12743897.1411602931000@Atlassian.JIRA>
References: <JIRA.12743897.1411602931000@Atlassian.JIRA>
 <JIRA.12743897.1411602931086@arcas>
Subject: [jira] [Created] (YARN-2600) if the container is killed during
 localization outstanding public cache localization tasks should be
 cancelled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sangjin Lee created YARN-2600:
---------------------------------

             Summary: if the container is killed during localization outstanding public cache localization tasks should be cancelled
                 Key: YARN-2600
                 URL: https://issues.apache.org/jira/browse/YARN-2600
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: nodemanager
    Affects Versions: 2.4.0
            Reporter: Sangjin Lee


We came across a situation (partly related with HDFS-7005) where a large number of public cache localization tasks were queued in the public localizer thread pool but the container is killed during localization (as it went over the timeout).

What's not helpful in this situation is that any work item that's queued will still be serviced by the resource localization service which is wasteful. And that may further delay localization efforts of other containers.

It would be good if we can cancel the pending localization tasks when the container is killed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)