[jira] [Commented] (MAPREDUCE-3178) Capacity Schedular shows incorrect cluster information in the RM logs

["Bhallamudi Venkata Siva Kamesh (Commented) (JIRA)" <ji...@apache.org>]

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

Bhallamudi Venkata Siva Kamesh commented on MAPREDUCE-3178:
-----------------------------------------------------------

When we start the NM again, as part of the registration, the following object will be created.

{code}
      RMNode rmNode = new RMNodeImpl(nodeId, rmContext, host, cmPort,
          httpPort, resolve(host), capability);
{code}

The above code internally calls  {code} context.getDispatcher().getEventHandler().handle(new NodeAddedSchedulerEvent(this)); {code}, which calls the CS#addNode() method. Here again this node's capability will be added to the clusterResource. In the mean time, the following part of the code throws exception

{code}
      if (this.rmContext.getRMNodes().putIfAbsent(nodeId, rmNode) != null) {
        throw new IOException("Duplicate registration from the node!");
      }
{code}
                
> 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: contrib/capacity-sched
>    Affects Versions: 0.24.0
>            Reporter: Bhallamudi Venkata Siva Kamesh
>
> 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