You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Arun C Murthy (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/24 20:36:32 UTC
[jira] [Resolved] (MAPREDUCE-3178) Capacity Schedular shows
incorrect cluster information in the RM logs
[ https://issues.apache.org/jira/browse/MAPREDUCE-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy resolved MAPREDUCE-3178.
--------------------------------------
Resolution: Duplicate
Will be fixed via MAPREDUCE-2775
> Capacity Schedular shows incorrect cluster information in the RM logs
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-3178
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3178
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Bhallamudi Venkata Siva Kamesh
> Assignee: Bhallamudi Venkata Siva Kamesh
> Priority: Blocker
> Attachments: MAPREDUCE-3178.patch
>
>
> When we start the NM, after stopping it (in a quick session) CS shows incorrect information about clusterResource in the logs.
> I have encountered this issue in a pseudo cluster mode and steps to reproduce are
> 1) start the YARN cluster
> 2) stop a NM and start the NM again (in a quick session)
> There should be a NM running in the cluster however as I observed RM detects NM as dead, after default time since its actual unavailability(In this case NM has been stopped).
>
> If you start your NM before this time (default time), ResourceTracker throws IOEx, however, CS adds the NM's capacity to the clusterResource.
> After elapsed time (default time) when RM detects NM as dead, RM removes the NM and hence capacity of the cluster will be subtracted by the amount NM capacity.
> Eventually there is no NM running in the cluster, but capacity of the cluster is NM's capacity (by default)
--
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