hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-686) Flatten NodeReport
Date Wed, 15 May 2013 20:39:15 GMT

     [ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandy Ryza updated YARN-686:
----------------------------

    Description: 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.
 (was: 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
moving the its two other methods, getHealthReport and getLastHealthReportTime, into NodeReport.)
    
> 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
>
> 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

Mime
View raw message