Details
-
Bug
-
Resolution: Done
-
Major
-
5.1.3.FINAL
-
None
Description
Hot Rod distribution tests have recently been failing with:
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)
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
