1 Reply Latest reply on Sep 18, 2014 10:52 AM by rvansa

HotRod Server Side Hashing

mohammedisaa.khan Sep 18, 2014 8:04 AM

Hi,

I am using Infinispan in distributed mode with hotrod client-server architecture. Currently i am facing a problem figuring out which key resides on which node in the cluster.

Since i am using hotrod, the hotrod is taking for hashing, balancing and key distribution. Hence the Infinispan API to locate primary owner of a segment/key shows inappropriate information.

A bit of code analysis revealed that through the hotrod client i can get the primary owner / main owner of the key. However i am unable to trace as to which node is the key is being transferred for back up.

Could somebody help me figure out how i can obtain - all the owners of a segment, all the owners of a key through hotrod?

1. Re: HotRod Server Side Hashing

rvansa Sep 18, 2014 10:52 AM (in response to mohammedisaa.khan)

With older versions of HotRod protocol (< 2.0), it's not that simple. Infinispan < 5.2 used different algorithms ('virtual nodes') while >= 5.2 uses 'segments'. In order to keep backward compatibility of clients, the server generates topology information that fits for > 99.9% (or some similar number) keys, but this does not contain backup owners, because HotRod clients don't have any notion of that.
AFAIK in HotRod 2.0

Checkout [ISPN-3529] Add support for the segment-based CH in the HotRod protocol - JBoss Issue Tracker - I am not familiar with the new implementation enough to comment about current state.
Actions