[
https://issues.apache.org/jira/browse/IGNITE-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249724#comment-16249724
]
Alexey Goncharuk commented on IGNITE-6870:
------------------------------------------
[~avinogradov] I am not working in TopologyValidator replacement, the only
probably change for this interface would be another method to handle toplogy
changes events (the ticket is IGNITE-6507). This ticket has nothing to do with
the change.
One of the ways to implement this metric is to look at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFutureAdapter#grpValidRes
which contains the result of caches validation
> Implement new JMX metric for cache topology validation monitoring
> -----------------------------------------------------------------
>
> Key: IGNITE-6870
> URL: https://issues.apache.org/jira/browse/IGNITE-6870
> Project: Ignite
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Labels: iep-6, jmx
>
> There is no way now to determine from outside the grid that cache is in
> read-only state after TopologyValidator's "validate" method returns "false"
> for topology.
> Implement new JMX metric in CacheMetricsMXBean to show cache's topology
> validation status.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
