[
https://issues.jboss.org/browse/ISPN-1578?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1578:
-----------------------------------
Summary: Send the base hash code for of each Hot Rod endpoint back to clients
(was: Send a byte[] along with each Hot Rod endpoint to use as hash seed)
Description:
Make Hot Rod server protocol 1.1 send a 32-bit hash or similar of the JGroups address, and
make both clients and servers hash on that.
The benefits of doing this, instead of relying on the Hot Rod endpoint are multiple, see
attached Infinispan Dev list thread for more info.
This requires changing Hot Rod protocol 1.1 which is introduced in 5.1:
https://docs.jboss.org/author/display/ISPN/Hot+Rod+Protocol+-+Version+1.1
This is pretty much going back to what we had in 1.0, except for the fact that we only
send one host:port:hashcode combo for each node, as opposed to for each virtual node. As
shown in the updated protocol documentation, this means that there's a contract now
set in terms of hash code normalization and virtual node hash code production.
This means as well that we don't need the hash seed functionality any more, at expense
of a few extra bytes in the payload.
was:
Make Hot Rod server protocol 1.1 send a 32-bit hash or similar of the JGroups address'
UUID back to client, and make both clients and servers hash on that.
The benefits of doing this, instead of relying on the Hot Rod endpoint are multiple, see
attached Infinispan Dev list thread for more info.
This requires changing Hot Rod protocol 1.1 which is introduced in 5.1:
https://docs.jboss.org/author/display/ISPN/Hot+Rod+Protocol+-+Version+1.1
Forum Reference:
http://lists.jboss.org/pipermail/infinispan-dev/2011-November/009563.html (was:
http://lists.jboss.org/pipermail/infinispan-dev/2011-November/009563.html)
Send the base hash code for of each Hot Rod endpoint back to clients
--------------------------------------------------------------------
Key: ISPN-1578
URL:
https://issues.jboss.org/browse/ISPN-1578
Project: Infinispan
Issue Type: Enhancement
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.CR1
Make Hot Rod server protocol 1.1 send a 32-bit hash or similar of the JGroups address,
and make both clients and servers hash on that.
The benefits of doing this, instead of relying on the Hot Rod endpoint are multiple, see
attached Infinispan Dev list thread for more info.
This requires changing Hot Rod protocol 1.1 which is introduced in 5.1:
https://docs.jboss.org/author/display/ISPN/Hot+Rod+Protocol+-+Version+1.1
This is pretty much going back to what we had in 1.0, except for the fact that we only
send one host:port:hashcode combo for each node, as opposed to for each virtual node. As
shown in the updated protocol documentation, this means that there's a contract now
set in terms of hash code normalization and virtual node hash code production.
This means as well that we don't need the hash seed functionality any more, at
expense of a few extra bytes in the payload.
--
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