The HotRod client should support a separate CH for each cache ------------------------------------------------------------- Key: ISPN-3530 URL: https://issues.jboss.org/browse/ISPN-3530 Project: Infinispan Issue Type: Feature Request Components: Remote protocols Affects Versions: 6.0.0.Alpha4 Reporter: Dan Berindei Assignee: Galder Zamarreño Labels: hotrod, hotrod-java-client With asymmetric clusters, each cache can have its own consistent hash, so the primary owner of a key in one cache is not necessarily the owner in all the caches. Even with a symmetric cluster, the same client may be used to access both distributed and replicated caches, and those would certainly have a different CH. In order to send the operations to the correct owner, the HotRod client should use a different CH for each cache.