[
https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678528#comment-13678528
]
Jian He commented on YARN-686:
------------------------------
we should move NodeHealthStatus to yarn.server.api.record after this patch,
also the 'NodeHealthStatus' can be moved from the NodeReport class comment.
Created YARN-792 for this.
> Flatten NodeReport
> ------------------
>
> Key: YARN-686
> URL: https://issues.apache.org/jira/browse/YARN-686
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.1.0-beta
>
> Attachments: YARN-686-1.patch, YARN-686.patch, YARN-686.patch
>
>
> The NodeReport returned by getClusterNodes or given to AMs in heartbeat
> responses includes both a NodeState (enum) and a NodeHealthStatus (object).
> As UNHEALTHY is already NodeState, a separate NodeHealthStatus doesn't seem
> necessary. I propose eliminating NodeHealthStatus#getIsNodeHealthy and
> moving its two other methods, getHealthReport and getLastHealthReportTime,
> into NodeReport.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
