hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18679) YARN may null Counters object and cause an NPE in ITBLL
Date Sat, 26 Aug 2017 04:01:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142602#comment-16142602

Hudson commented on HBASE-18679:

FAILURE: Integrated in Jenkins build HBase-2.0 #397 (See [https://builds.apache.org/job/HBase-2.0/397/])
HBASE-18679 Add a null check around the result of getCounters() in ITBLL (elserj: rev b55b952d5c5e90bde03f454500e867b7909fea75)
* (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

View raw message