Last night I spoke at the Dusseldorf JUG and had a very nice time with one exception: I broke my last demo. YIPE!
I have suffered for hours since then going over my code and trying to see where I dropped the ball and finally, looking elsewhere, have come upon the reason!
The default setting for replication in the cluster configuration that I selected for the demo in GigaSpaces 6.0 XAP is sync-rec-ack. sync-rec-ack defines the replication behavior to be ‘nearly synchronous’ with the client thread blocking only long enough to ensure that the request has been sent – not received – by the backup space.
I changed the setting to fully synchronous – called ‘sync’ in our configuration, and things are much much better. Now, I understand how Virgin Mobile succeeded with our technology where I failed. (they use the sync setting).
For those of you who were watching, my apologies for losing that one order when I killed both of the primary spaces as it was running. With this new improvement, I swear it won’t happen again!