[
https://issues.apache.org/jira/browse/HBASE-19317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263766#comment-16263766
]
Hudson commented on HBASE-19317:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-2.0 #899 (See
[https://builds.apache.org/job/HBase-2.0/899/])
HBASE-19317 Set a high NodeManager max disk utilization if not already (elserj:
rev 4e387a948fad9928c9d4922c9055e601d22e4145)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
> Increase
> "yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage"
> to avoid host-related failures on MiniMRCluster
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-19317
> URL: https://issues.apache.org/jira/browse/HBASE-19317
> Project: HBase
> Issue Type: Bug
> Components: integration tests, test
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19317.001.branch-2.patch,
> HBASE-19317.002.branch-2.patch
>
>
> YARN (2.7.4, at least) defaults to asserting at least 10% of the disk usage
> free on the local machine in order for the NodeManagers to function.
> On my development machine, despite having over 50G free, I would see the
> warning from the NM that all the local dirs were bad which would cause the
> test to become stuck waiting to submit a mapreduce job. Surefire would
> eventually kill the process.
> We should increase this value to avoid it causing us headache.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
