[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1091:
----------------------------------------
I have my doubts about dealing in the same way with timeout or repl timeout exceptions. A
suspect exception is a clear thing cos you want to repeat the operation cos the node was
suspected and so it's no longer part of the cluster. But for timeouts, any retry would
make sense with a back-off of some sort to avoid too many lock acquisition contention. For
the moment I'm gonna leave this out and focus on what needs fixing immediately which
is the suspect exception.
HotRod clients should failover if encountering a SuspectException
-----------------------------------------------------------------
Key: ISPN-1091
URL:
https://issues.jboss.org/browse/ISPN-1091
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.1.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.2.BETA1, 4.2.2.FINAL, 5.0.0.CR3
As Michal rightly indicated in JBPAPP-6473, Hot Rod clients need to be able to deal with
SuspectException errors and failover rather than bubbling up. In the future the server
will make sure the right error code is returned, but in the absence of that, the error
message can be inspected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira