[infinispan-issues] [JBoss JIRA] (ISPN-1855) Accessing a non-distributed cache from a RemoteCacheManager can break topology updates

[Dan Berindei (JIRA)]

Dan Berindei created ISPN-1855:
----------------------------------

             Summary: Accessing a non-distributed cache from a RemoteCacheManager can break topology updates
                 Key: ISPN-1855
                 URL: https://issues.jboss.org/browse/ISPN-1855
             Project: Infinispan
          Issue Type: Bug
    Affects Versions: 5.1.1.FINAL
            Reporter: Dan Berindei
            Assignee: Manik Surtani
             Fix For: 5.2.0.FINAL


RemoteCacheManager uses a single consistent hash to map requests to different servers, but caches on the server may have different CHs (or even no CH if the cache is not in distributed mode).

If the first request goes to a on-distributed cache, the client will never request an updated CH and so it will use a round robin strategy for routing request to all the caches. Obviously this is not optimal for distributed caches.

Each distributed cache can also have different members since 5.1, so it would be best if we kept a separate CH per cache on the client.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira