Resolution: Won't Fix
Affects Version/s: 0.23.0, 2.0.0-alpha
Fix Version/s: None
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.
|Priority||Major [ 3 ]||Critical [ 2 ]|
|Affects Version/s||0.23.0 [ 12315570 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Won't Fix [ 2 ]|
|Affects Version/s||2.0.0-alpha [ 12320354 ]|
|Affects Version/s||0.24.0 [ 12317654 ]|