[
https://issues.jboss.org/browse/ISPN-3604?page=com.atlassian.jira.plugin....
]
Duncan Doyle commented on ISPN-3604:
------------------------------------
Idea is to refactor 'org.infinispan.tasks.GlobalKeySetTask'. That implementation
currently does not take entries in the CacheLoader into account. So I want to change that
implementation to use the implementation of
'org.infinispan.server.hotrod.util.BulkUtil' and make the HotRod server use the
GlobalKeySetTask.
I want to implement the JMX operation on the 'org.infinispan.CacheImpl', as the
'org.infinispan.interceptors.CacheMgmtInterceptor' is not really the correct place
for it (first of all, it is not data that is collected via an interceptor (i.e., we use a
Map/Reduce function), second the data is not really statistics data (i.e. it's the
current global number of keys in the grid), third I don't actually have access to the
Cache object in the interceptor code ....).
Any comments?
Provide JMX operation which shows the numberOfEntries in the entire
dist-cache
------------------------------------------------------------------------------
Key: ISPN-3604
URL:
https://issues.jboss.org/browse/ISPN-3604
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management
Affects Versions: 6.0.0.CR1
Environment: Max OS-X 10.8.5, Oracle Hotspot 1.7.0_40, Infinispan 5.2.4.Final
Reporter: Duncan Doyle
Assignee: Mircea Markus
The Infinispan statistics component only shows the 'numberOfEntries' in a
particular node, including entries of which the node is not the primary owner (basically,
doing a sum of this value of all the cluster members gives you (numberOfEntries *
numOwners). The 'cache.keySet()' method does return the entire keyset, and thus
you can calculate the numberOfEntries in the cache, but this requires writing custom code
in a cache client. It would be nice if Infinispan would provide a JMX operation which is
able to show the number of entries in the entire dist-cache cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira