-
Task
-
Resolution: Duplicate
-
Major
-
5.2.0.Final
This is an extension of ISPN-1896 of sorts, but for all the cache operations that are visible to the user.
After a node leaves, the other nodes that have sent commands to that node should either ignore SuspectExceptions or, if not possible, they should retry the operation (e.g. if they didn't get any response back).
For example, VersionReplStateTransferTest quite often on my machine with a SuspectException, because the versioned prepare command expects a response from the coordinator and the coordinator has just left.
- blocks
-
ISPN-2935 After view change single node is left in cluster, but still tries to invoke stuff remotely
- Closed
-
ISPN-2515 VersionedReplStateTransferTest.testStateTransfer fails randomly
- Closed
-
ISPN-2608 VersionedDistStateTransferTest intermittent failure
- Closed
- incorporates
-
ISPN-2577 Silence SuspectExceptions
- Closed
-
ISPN-1896 ClusteredGetCommands should never fail with a SuspectException
- Closed
- is related to
-
ISPN-2648 org.infinispan.query.distributed.MultiNodeReplicatedTest.testIndexingWorkDistribution() test randomly fails
- Closed
- relates to
-
ISPN-2510 PrepareCommands should fail on nodes where the cache is not running
- Closed