[infinispan-issues] [JBoss JIRA] (ISPN-3947) HotRod client keep trying recover connections to a failed cluster
[
https://issues.jboss.org/browse/ISPN-3947?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-3947:
------------------------------------
[~wfink] The thing is, we never retry on the same server. We retry on a random server
regardless of where the key maps to, because it's better to hit the "wrong"
server than to hit no server at all. It's true that picking a random server means
it's also possible to get the same server every time, but that would be very
unlikely.
This is similar to how {{numOwners}} is fixed in a distributed cache, regardless of the
cluster size. Since {{numOwner}} server failures in a short interval of time would cause
data loss anyway, throwing an exception should also be ok.
HotRod client keep trying recover connections to a failed cluster
-----------------------------------------------------------------
Key: ISPN-3947
URL: https://issues.jboss.org/browse/ISPN-3947
Project: Infinispan
Issue Type: Feature Request
Components: Remote Protocols
Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
Reporter: Wolf-Dieter Fink
Assignee: Galder Zamarreño
Labels: hotrod, hotrod-java-client
If an infinispan-server cluster is not longer reachable for some reason, i.e. network
disconnect, the hot-rod client try to re-establish the lost connections.
The client library will retry this by a fixed calculation based on the max numbers of
connections from the pool or 10 multiplied with the number of available servers.
This can lead in a very long time until the application can continue and react as it will
wait for the read- or connect-timeout for each try.
To improve this behaviour there should be a configurable limit of retries per server
and/or a timeout in total.
This will give the application the chance to handle a remote-cache failure and reply to
the user instead of hanging for minutes (with the default settings)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira