On 5 Nov 2010, at 14:20, Vladimir Blagojevic wrote:
On 10-11-05 5:39 AM, Manik Surtani wrote:
> Shouldn't you count down after receivers have applied the state, and have then
ack'd that this state has been applied? Rather than when the state has been picked
up?
I thought about that but I think there is no need. I have to think
throught the details though. The main idea was since the state is a
simple message sent from a state provider eventual tx log message sent
from state provider as well is guaranteed to arrive after state message.
Right?
State is provided as result of a pull, so after the provider responds with
the state, it might take time to the receiver to integrate it. If we send tx log during
that time, we have no ordering guarantee.
> Rather than a countdown latch, wouldn't you rather maintain a synchronized set or
something with the addresses of the recipients, and you only proceed when this set is
empty? Tighter control rather than a simple countdown.
Right, of course. I first wanted to see if I can get away cheaply :)
> Also, how do you plan on dealing with exceptional circumstances, e.g., a receiver
node crashing before sending this ack? Would that not block the entire rehash process?
Or would the node crashing cause a new view change, which will abort the LeaveTask
(interrupt) and cause it to start all over again?
Yes, we would definetely need timeouts...and proper interrupt handling.
Cheers.
> Cheers
> Manik
> --
> Manik Surtani
> manik(a)jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
>
http://www.infinispan.org
>
http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev