[
https://issues.apache.org/jira/browse/MAPREDUCE-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162607#comment-13162607
]
Devaraj K commented on MAPREDUCE-3363:
--------------------------------------
This issue will cause a huge loss, if multiple nodes restart at a time, and due
to the false cluster capacity assumed, many jobs will fail in the cluster,
which is a performance hit.
> 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.24.0
> Reporter: Ramgopal N
> Assignee: Devaraj K
> 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
