Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Thu, 22 Jan 2015 20:57:35 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12769439.1421960202000.150402.1421960255208@Atlassian.JIRA>
In-Reply-To: <JIRA.12769439.1421960202000@Atlassian.JIRA>
References: <JIRA.12769439.1421960202000@Atlassian.JIRA>
 <JIRA.12769439.1421960202444@arcas>
Subject: [jira] [Created] (YARN-3090) DeletionService can silently ignore
 deletion task failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jason Lowe created YARN-3090:
--------------------------------

             Summary: DeletionService can silently ignore deletion task failures
                 Key: YARN-3090
                 URL: https://issues.apache.org/jira/browse/YARN-3090
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
    Affects Versions: 2.1.1-beta
            Reporter: Jason Lowe


If a non-I/O exception occurs while the DeletionService is executing a deletion task then it will be silently ignored.  The exception bubbles up to the thread workers of the ScheduledThreadPoolExecutor which simply attaches the throwable to the Future that was returned when the task was scheduled.  However the thread pool is used as a fire-and-forget pool, so nothing ever looks at the Future and therefore the exception is never logged.


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