[
https://issues.jboss.org/browse/ISPN-842?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-842:
---------------------------------------
Oh right, I remember the use case. It's the same as with HTTP sessions. The
FirstAvailable, or sticky load balance policy, would for a particular key chose a node,
and then all further requests for that key direct to the same node unless there's a
failure. This allows for replicated caches to be configured with async comms cos the
possibilities of landing on a different node to work on a key are reduced. I haven't
seen demand in the user forums, but something worth keeping in mind.
FirstAvailable load balance policy for Hot Rod clients and extend
reach of load balance policies
------------------------------------------------------------------------------------------------
Key: ISPN-842
URL:
https://issues.jboss.org/browse/ISPN-842
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Mircea Markus
Create a FirstAvailable load balance policy for Java Hot Rod clients and make sure load
balance policies
are used by all operations, particularly those extending AbstractKeyOperation.
See forum thread for more info.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira