Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Won't Fix
-
0.23.0, 2.0.0-alpha
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-3585 RM unable to detect NMs restart
- Resolved
- is related to
-
MAPREDUCE-3070 NM not able to register with RM after NM restart
- Closed
- relates to
-
MAPREDUCE-3271 Lost nodes list and count not updated
- Resolved
-
YARN-41 The RM should handle the graceful shutdown of the NM.
- Resolved