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

Akira Ajisaka commented on YARN-3254:
-------------------------------------

bq. Would you mind if I take over this JIRA if you are not working on this 
currently ?
No. You can take it over.

bq. Also, can you please explain why the patch is incompatible with jmx 
information being changed ?
This health report is obtained from jmx. Accoding to the documentation 
(https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html#MetricsJMX),
 changing the jmx information breaks compatibility. Now I'm thinking you can 
add the message to the Web UI if you create an additional jmx information and 
use it.

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