Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 24 Aug 2017 22:00:04 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13097440.1503611500000.116194.1503612004384@Atlassian.JIRA>
In-Reply-To: <JIRA.13097440.1503611500000@Atlassian.JIRA>
References: <JIRA.13097440.1503611500000@Atlassian.JIRA> <JIRA.13097440.1503611500621@jira-lw-us.apache.org>
Subject: [jira] [Updated] (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
archived-at: Thu, 24 Aug 2017 22:00:10 -0000


     [ https://issues.apache.org/jira/browse/HBASE-18679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated HBASE-18679:
-------------------------------
    Attachment: HBASE-18679.001.patch

.001 Really trivial patch -- checks if the {{Counters}} object is null, and bails out fast (failing verification) when it happens.

Nothing we can do in hbase-landia, user has to remedy via their configuration.

> 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
>
>
> 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)