hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-3363) The "totalnodes" and "memorytotal" fields show wrong information if the nodes are going down and coming up early(before 10min)
Date Fri, 17 Feb 2012 00:36:01 GMT

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

Vinod Kumar Vavilapalli resolved MAPREDUCE-3363.
------------------------------------------------

    Resolution: Won't Fix

Agree with Jason. Because NMs bind to ephemeral ports, it is not possible to make sure that
it is the same node.

Arguably 10 minutes is too long a time with the YARN's (ultra cool ;) ) infrastructure, so
we plan to lessen it by default. That should mitigate the issue a bit.
                
> The "totalnodes"  and "memorytotal" fields show wrong information if the nodes are going
down and coming up early(before 10min) 
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3363
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3363
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Ramgopal N
>            Priority: Critical
>         Attachments: Applications.htm, screenshot-1.jpg
>
>
> The node details is not moved from Totalnodes to lostnodes for 600000 ms.So if the node
is going down and coming up before the expiry interval, the cluster status in terms of the
total nodes and Total cluster memory displays wrong values. 
> Atleast, if the same node is coming up again...should not consider as new node.No point
of time duplicate nodes should be displayed in Totalnodes list.

--
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

        

Mime
View raw message