[jira] [Commented] (AMBARI-14524) HDFS Recommendation: dfs.datanode.du.reserved should be set to 10%-15% of volume size

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-14524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075094#comment-15075094 ] 

Hadoop QA commented on AMBARI-14524:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12779978/AMBARI-14524.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4740//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4740//console

This message is automatically generated.

> HDFS Recommendation: dfs.datanode.du.reserved should be set to 10%-15% of volume size
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14524
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14524
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14524.patch
>
>
> PROBLEM: Ambari should give recommendations on this setting: dfs.datanode.du.reserved
> The default is 1GB and that is too low for a lot of our production customers. If this is too low and the space on the datanode fills up, the nodemanagers will start failing the health checks and we get into a bad state with not enough nodemanagers being up. At this point the admin tries to run the balancer and hope that it will balance very quickly.
> There should be a recommendation on this value based on the disk space available in the datanode volume. In addition, if the user sets it too low there should be a warning saying this will cause problems if enough buffer is not kept.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)