[infinispan-issues] [JBoss JIRA] (ISPN-2817) Expose locate(key) on the java RemoteCacheManager
Mircea Markus (JIRA)
jira-events at lists.jboss.org
Tue Feb 12 09:14:56 EST 2013
[ https://issues.jboss.org/browse/ISPN-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753672#comment-12753672 ]
Mircea Markus commented on ISPN-2817:
-------------------------------------
[~galder.zamarreno] has a fair point that this approach operation doesn't scale:
{quote}If you go down that path you're gonna have to identify all JMX operations that have a key as parameter or return, and duplicate those operations. Next time someone adds an operation, we'll have to make sure we don't end up having the same problem. {quote}
If we'll get more such requirements we can potentially enhance the Hot Rod protocol itself with a generic method of querying the server for such stats. The approach suggested in this JIRA's description is easy to implement and solves the problem of the clients that need it.
> Expose locate(key) on the java RemoteCacheManager
> -------------------------------------------------
>
> Key: ISPN-2817
> URL: https://issues.jboss.org/browse/ISPN-2817
> Project: Infinispan
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 5.2.1
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 5.3.0.Final
>
>
> RemoteCache.locate(key) method would return the server endpoints (or/and the actual JGroups address?) where the given key maps (a sequence, first being the primary owner).
--
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
More information about the infinispan-issues
mailing list