[infinispan-issues] [JBoss JIRA] Commented: (ISPN-271) Expose global information in RpcManagerImpl via CacheManager
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Tue Feb 1 14:16:39 EST 2011
[ https://issues.jboss.org/browse/ISPN-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579436#comment-12579436 ]
Galder Zamarreño commented on ISPN-271:
---------------------------------------
To clarify, since RpcManagerImpl/RpcManager have no scope, it means that they're scoped at a cache level. So, the following JMX attributes are calculated on a per cache basis:
AverageReplicationTime
ReplicationCount
ReplicationFailures
SuccessRatio
SuccessRatioFloatingPoint
However, the following information comes from Transport, which is a global component, so this JMX info is redundant and will be available via the Cache Manager JMX Mbean instead:
ClusterSize
Members
NodeAddress
PhysicalAddresses
> Expose global information in RpcManagerImpl via CacheManager
> ------------------------------------------------------------
>
> Key: ISPN-271
> URL: https://issues.jboss.org/browse/ISPN-271
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management, RPC
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Labels: hackathon
> Fix For: 5.0.0.ALPHA3, 5.0.0.Final
>
>
> RpcManagerImpl exposes information that are both global to all caches under a cache manager and information that is specific to a cache.
> An idea would be to expose any global information via CacheManager mbean instead, i.e. address, cluster members
> And the rest, stuff that is cache specific, expose via rpc manager mbean,
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list