[infinispan-dev] rehashing hazard

[Vladimir Blagojevic]

>> 
>> The operations that need to be sequential are state transfer and tx log transfer. 
>> State is being *pulled* by C (thread running on C) and tx log is *pushed* by A (thread running on A). Two threads running in different VMs. 
> 
> Ok, this would be the issue then - this must have changed when Vladimir inverted the leave task to be a pull for the main state.  They both used to be pushes and sequential.
> 
> Perhaps the sequentiality can be re-established by a lock on the receiver?

Interested. What if C thread announce that it pulled state and upon reception of this message A drains the logs?