-
Enhancement
-
Resolution: Done
-
Major
-
6.0.0.Final
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.
- blocks
-
ISPN-3533 Design HotRod protocol version 2.0
- Closed
- is related to
-
ISPN-3729 Minimize the number of moved segments for SyncConsistentHashFactory
- Closed
-
ISPN-3529 Add support for the segment-based CH in the HotRod protocol
- Closed
- relates to
-
ISPN-3701 In HotRod client topologyId is shared for all caches
- Resolved
-
ISPN-1855 Accessing a non-distributed cache from a RemoteCacheManager can break topology updates
- Closed
-
ISPN-4212 Unable to get entries from newly started non-defined caches
- Closed