Hello.
We are using pessimistic transaction mode. In this case everything's already
locked by the time of prepare, is not it?
As of merge, for quorum mode it's simple - take data from quorum. I think I
will try to simply suppress sending data from non-quorum members on merge.
Because
Well, I don't do SYNCHRONOUS_IGNORE_LEAVERS for commands that has less than
quorumSize number of destinations (so commands to single destination retain
it's ResponseMode unchanged) and recheck after the command that I still have
enough member in the cluster. But I will add a test to check that
Hello.
Thanks for your information. I will subscribe and vote for the issues noted.
In the meantime I've implemented hacky JgroupsTransport that downgrades all
(but CacheViewControlCommand and StateTransferControlCommand) SYNCHRONOUS
invokeRemotely calls to SYNCHRONOUS_IGNORE_LEAVERS and checks
