Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C9044200B17 for ; Mon, 6 Jun 2016 23:40:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C79AA160A1E; Mon, 6 Jun 2016 21:40:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 260F3160A24 for ; Mon, 6 Jun 2016 23:40:22 +0200 (CEST) Received: (qmail 70189 invoked by uid 500); 6 Jun 2016 21:40:21 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 70161 invoked by uid 99); 6 Jun 2016 21:40:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2016 21:40:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0AF6F2C1F5D for ; Mon, 6 Jun 2016 21:40:21 +0000 (UTC) Date: Mon, 6 Jun 2016 21:40:21 +0000 (UTC) From: "Carlo Curino (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5185) StageAllocaterGreedyRLE: NPE in corner case MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 06 Jun 2016 21:40:23 -0000 [ https://issues.apache.org/jira/browse/YARN-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317311#comment-15317311 ] Carlo Curino commented on YARN-5185: ------------------------------------ [~asuresh], this bug is very similar to what we had in YARN-4525, for which I was able to construct a test. Here it is tricky, as the bug only triggers once the NavigableMap is accessed and restricted multiple times, and the use is fairly deep into the stack of calls we can test. However (answering your question), I saw tests in YARN-5164 triggering this bug. I am ok merging this or not as you prefer. I think the patch is fairly clearly non-harmful and protects against a possible NPE so I would suggest to commit it as is, because the reviewing of YARN-5164 is less trivial, and actually quite delicate. > StageAllocaterGreedyRLE: NPE in corner case > -------------------------------------------- > > Key: YARN-5185 > URL: https://issues.apache.org/jira/browse/YARN-5185 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler, fairscheduler, resourcemanager > Reporter: Carlo Curino > Assignee: Carlo Curino > Attachments: YARN-5185.1.patch > > > If the plan has only one interval, and the reservation exactly overlap we will have a null from partialMap.higherKey() that we should guard against. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org