[jbosscache-dev] Cache unable to write to cluster

[Bela Ban]

That's what I meant: FLUSH itself already listens for view changes...

Brian Stansberry wrote:
> Bela Ban wrote:
>>
>>
>> Manik Surtani wrote:
>>> Ok - so we could add an extra check into the view change listener to 
>>> force an unblock if a member who initiated a FLUSH dies.  We would 
>>> also have to record the address of the member initiating the FLUSH 
>>> in the flushBlockGate.
>>
>> +1.
>>
>
> Shouldn't this be handled by FLUSH itself? MembershipListener.block() 
> doesn't provide any information on who the flush coordinator is, so 
> JBC has no way to implement Manik's suggestion. But FLUSH itself 
> should know enough to detect the view change and trigger an unblock().
>
> BTW, I see that the AS ClusterPartition has the same weakness.
>
>

-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat