9:21 a.m.
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.CR2
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
3:28 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1091:
----------------------------------------
To sump up some of the discussion happening in JBPAPP-6473, the server should not be the
one doing the failover if it receives a SuspectException or similar out of a cache
invocation. It should launder it and bubble it up to the client who's the one
ultimately making the decision to failover or not.
Also, as rightly pointed out by Michal, we should check what happens with repl timeout
exception. AFAIK, this should have been covered under the 0x86 command timed out status
code in http://community.jboss.org/docs/DOC-14421 and if that's the case, it should
failover already. If it's not, it needs changing.
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.CR2
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
4:48 a.m.
New subject: [JBoss JIRA] Work started: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Work on ISPN-1091 started by Galder Zamarreño.
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.CR2
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
6:51 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1091:
-----------------------------------
Fix Version/s: 5.0.0.CR3
(was: 5.0.0.CR2)
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
6:51 a.m.
New subject: [JBoss JIRA] Work stopped: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Work on ISPN-1091 stopped by Galder Zamarreño.
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
10:48 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
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
11:04 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1091:
-----------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/311
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
11:06 a.m.
New subject: [JBoss JIRA] Work started: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Work on ISPN-1091 started by Galder Zamarreño.
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
6:37 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-1091) HotRod clients should failover if encountering a SuspectException
[
https://issues.jboss.org/browse/ISPN-1091?page=com.atlassian.jira.plugin....
]
Mircea Markus resolved ISPN-1091.
---------------------------------
Resolution: Done
integrated.
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
4970
days inactive
4977
days old
infinispan-issues@lists.jboss.org
8 comments
2 participants
participants (2)
-
Galder Zamarreño (JIRA) -
Mircea Markus (JIRA)