[
https://issues.apache.org/jira/browse/IGNITE-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276417#comment-16276417
]
Aleksey Plekhanov commented on IGNITE-6867:
-------------------------------------------
[~vozerov]
# Perhaps, it's better to leave cluster and local node metrics as is (to show
statistics), and create new bean for topology (for example, ClusterInfo or
IgniteCluster)?
# Ok, I agree
# I don't understand purpose of {{attributeNames}} and {{attributeValues}}
methods? To show distinct attribute names in entire cluster and distinct values
of this attribute in entire cluster? I don't think this information without
binding to nodes is useful at all. Other methods in proposed API don't solve
our needs. They solves only part of the problem (filter by attribute value). We
need also some grouping operation (for example, we have nodes in different data
centers, the information about data center is stored in the node attributes, we
need to determine how many nodes in each data center left). Maybe is better to
just rename the methods (for example, countNodesGroupedByAttribute,
countNodesFilteredByAttribute)?
> Implement new JMX metrics for topology monitoring
> -------------------------------------------------
>
> Key: IGNITE-6867
> URL: https://issues.apache.org/jira/browse/IGNITE-6867
> Project: Ignite
> Issue Type: New Feature
> Reporter: Aleksey Plekhanov
> Assignee: Pavel Pereslegin
> Labels: iep-6, jmx
> Fix For: 2.4
>
>
> These additional metrics and methods should be implemented:
> * Current topology version
> * Total server nodes count
> * Total client nodes count
> * Method to count nodes filtered by some node attribute
> * Method to count nodes grouped by some node attribute
>
> There is already a ticket to implement first 2 metrics from this list
> (IGNITE-6844)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
