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 Security Level: Public(Everyone can see) Components: Remote Protocols Affects Versions: 5.1.1.FINAL Reporter: Dan Berindei Assignee: Galder Zamarreño Fix For: 7.0.0.Alpha5 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.