Just doing simple tests with two data nodes and one non-data node. Deploying kibana 4.3 and ES 2.1 from scratch.
Initially marvel is showing 3 nodes, all is green and peachy. If I stop and a node, Marvel shows it's down. However when I start the node entry seem to be somehow 'duplicated'
In Marvel 2.1, we made the design decision to group nodes in the listing by UID, rather than name or IP / port number. There are different ways it could be done. Grouping by UID is accurate in the sense that when you start a node, it is a new and distinct node, even if other meta information about it is the same, such as name as a node that has been in the cluster before. In fact, there is no restriction for multiple nodes in the cluster to share the same name. UID is unique though, which is why we thought it makes sense to group node data by node UID.
We're looking into changing the grouping of the listing to be grouped by node name as opposed to node UID, because it's easy to see now how the results become confusing.
Note that the "offline" nodes will be removed from the list when your selected time window moves past the period that those nodes had uptime. In other words, "Offline" status means that at some time during the time range you have selected, there was a node with that name online, but as of the time at the right-most edge of that range, that node was not online.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
