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

Suma Shivaprasad commented on YARN-3254:
----------------------------------------

Updated the patch to display the exact root cause for the disk error/capacity 
exceeded cases. These error diagnostics were already available in 
DirectoryCollection earlier but was ignored and  not surfaced in the health 
report. Along with the ratio of disks marked as unhealthy for local/log dirs, 
the reason why each of them was marked unhealthy will be surfaced in health 
report. Sample errors below

{noformat}
1/1 local-dirs have errors: [ /invalidDir1 : Cannot create directory: 
/invalidDir1 ] 1/1 log-dirs usable space is below configured utilization 
percentage/no more usable space [ /hadoop-3.0.0-beta1-SNAPSHOT/logs/userlogs : 
used space above threshold of 1.0% ]

 

> HealthReport should include disk full information
> -------------------------------------------------
>
>                 Key: YARN-3254
>                 URL: https://issues.apache.org/jira/browse/YARN-3254
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: Akira Ajisaka
>            Assignee: Suma Shivaprasad
>             Fix For: 3.0.0-beta1
>
>         Attachments: Screen Shot 2015-02-24 at 17.57.39.png, Screen Shot 
> 2015-02-25 at 14.38.10.png, YARN-3254-001.patch, YARN-3254-002.patch, 
> YARN-3254-003.patch, YARN-3254-004.patch
>
>
> When a NodeManager's local disk gets almost full, the NodeManager sends a 
> health report to ResourceManager that "local/log dir is bad" and the message 
> is displayed on ResourceManager Web UI. It's difficult for users to detect 
> why the dir is bad.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to