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 A0EC7200D10 for ; Sat, 26 Aug 2017 04:04:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9F88216DA4C; Sat, 26 Aug 2017 02:04:08 +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 E74DE16DA48 for ; Sat, 26 Aug 2017 04:04:07 +0200 (CEST) Received: (qmail 95963 invoked by uid 500); 26 Aug 2017 02:04:07 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 95952 invoked by uid 99); 26 Aug 2017 02:04:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Aug 2017 02:04:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8323CC1D1F for ; Sat, 26 Aug 2017 02:04:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id S68EgdUKBxyZ for ; Sat, 26 Aug 2017 02:04:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7C9125FCB9 for ; Sat, 26 Aug 2017 02:04:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 18D94E0D49 for ; Sat, 26 Aug 2017 02:04:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E093A25385 for ; Sat, 26 Aug 2017 02:04:00 +0000 (UTC) Date: Sat, 26 Aug 2017 02:04:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18679) YARN may null Counters object and cause an NPE in ITBLL MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 26 Aug 2017 02:04:08 -0000 [ https://issues.apache.org/jira/browse/HBASE-18679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142548#comment-16142548 ] Hudson commented on HBASE-18679: -------------------------------- FAILURE: Integrated in Jenkins build HBase-1.5 #32 (See [https://builds.apache.org/job/HBase-1.5/32/]) HBASE-18679 Add a null check around the result of getCounters() in ITBLL (elserj: rev fd43879985547eb05e04bed4c91feea7eac977c3) * (edit) hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestBigLinkedList.java > YARN may null Counters object and cause an NPE in ITBLL > ------------------------------------------------------- > > Key: HBASE-18679 > URL: https://issues.apache.org/jira/browse/HBASE-18679 > Project: HBase > Issue Type: Bug > Components: integration tests > Reporter: Josh Elser > Assignee: Josh Elser > Priority: Trivial > Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13 > > Attachments: HBASE-18679.001.patch, HBASE-18679.002.patch > > > YARN has a configuration limit to the number of counters that a job can create (to avoid some bad job from DDOS'ing the service). > When running ITBLL, we ran into this limit due to the default configuration rather low at the time. When YARN notices that the counter limit has been exceeded, it nulls out the Counters object obtained by the Job. > Presently in ITBLL, we have a few places where we (reasonably ;)) assume that the Counters object would be non-null. Can easily fix this with a null-check. -- This message was sent by Atlassian JIRA (v6.4.14#64029)