[
https://issues.jboss.org/browse/ISPN-1998?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-1998:
-------------------------------------
I'll take this. The problem here is that the suspect exception should not bubble up
and cause a transaction failure. If the node is gone and cannot be invalidated, then too
bad. No biggie.
Suspect exception for InvalidateL1Command after node leaving and
doing a put
----------------------------------------------------------------------------
Key: ISPN-1998
URL:
https://issues.jboss.org/browse/ISPN-1998
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 5.1.3.FINAL
Reporter: Galder Zamarreño
Assignee: Dan Berindei
Fix For: 5.1.4.FINAL
Hot Rod distribution tests have recently been failing with:
{code}Caused by: java.util.concurrent.ExecutionException:
org.infinispan.remoting.transport.jgroups.SuspectException: One or more nodes have left
the cluster while replicating command SingleRpcCommand{cacheName='hotRodDistSync',
command=InvalidateL1Command{num keys=1, forRehash=false,
origin=HotRodDistributionTest-NodeA-24419}}
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.infinispan.interceptors.DistributionInterceptor.handleWriteCommand(DistributionInterceptor.java:518)
at
org.infinispan.interceptors.DistributionInterceptor.visitPutKeyValueCommand(DistributionInterceptor.java:272){code}
This happens once a node goes down, after waiting for the cluster view to reform, when a
client does a put() on one of the other surviving nodes.
The two suspicious things here are:
* Why is an error on InvalidateL1Command bubbling up? If anything, it should be the put
that fails to work.
* Why would a suspect exception happen even if you wait for the cluster to reform?
Note that these Hot Rod server tests use a simplistic Hot Rod client that does not filter
suspect exceptions...etc
--
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