[
https://issues.apache.org/jira/browse/MAPREDUCE-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396130#comment-13396130
]
Karthik Kambatla commented on MAPREDUCE-4288:
---------------------------------------------
In YARN, the ClusterMetrics should only correspond to numNodeManagers,
numActiveJobs(), numActiveContainers(), availableResources(). Other
job/app-specific metrics should move to the corresponding AMs. JobStatus would
be a good place to have these metrics.
Subsequently, JobClient.getClusterStatus() can correspond to the job-specific
metrics (would be a misnomer).
Comments?
> ClusterStatus.getMapTasks() and ClusterStatus.getReduceTasks() is giving one
> when no job is running
> ---------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4288
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4288
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha
> Reporter: Nishan Shetty
> Assignee: Karthik Kambatla
>
> When no job is running in the cluster invoke the ClusterStatus.getMapTasks()
> and ClusterStatus.getReduceTasks() API's
> Observed that these API's are returning one instead of zero(as no job is
> running)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
