Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7966118A8F for ; Fri, 13 Nov 2015 15:52:13 +0000 (UTC) Received: (qmail 76405 invoked by uid 500); 13 Nov 2015 15:52:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 76187 invoked by uid 500); 13 Nov 2015 15:52:11 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 75823 invoked by uid 99); 13 Nov 2015 15:52:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Nov 2015 15:52:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 057BA2C1F5D for ; Fri, 13 Nov 2015 15:52:11 +0000 (UTC) Date: Fri, 13 Nov 2015 15:52:11 +0000 (UTC) From: "Jason Lowe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4354) Public resource localization fails with NPE MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004157#comment-15004157 ] Jason Lowe commented on YARN-4354: ---------------------------------- I believe this was caused by YARN-2902. A resource was just localized, but the resource is missing. That normally doesn't occur. However after YARN-2902 a resource can be yanked out while it is still downloading if a container releases it and the refcount is zero. So if a public resource is requested by a container but killed before the localization completes then we can get a localized event for a missing resource and hit the NPE. We should not be removing a resource if the localization will still complete, otherwise we not only risk the NPE but also leaking the local files. > Public resource localization fails with NPE > ------------------------------------------- > > Key: YARN-4354 > URL: https://issues.apache.org/jira/browse/YARN-4354 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 2.7.2 > Reporter: Jason Lowe > Priority: Blocker > > I saw public localization on nodemanagers get stuck because it was constantly rejecting requests to the thread pool executor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)