Semi-optimistic concurrency to handle multiple grain activations about orleans.activities HOT 2 CLOSED

A perfect description of the lease/lock (an analysis of the redlock): http://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html

In my approach, we don't need expiration, that's given by Orleans, each grain state read breaks any previous lease (possible dead previous grain) and starts it's own. In case the previous grain is not dead, it won't be able to write back it's state and will abort the workflow immediately, though in this case (etag violation) a forced deactivation would be better.

See also:

• http://stackoverflow.com/questions/35248830/how-to-handle-split-brain
• dotnet/orleans#1420 (Deactivate grains upon write conflict)

So I plan to add later an optional break/lease step into Orleans blob storage provider.

I don't know Orleans' activation algorithms, may be this issue is unnecessary/overkill.

from orleans.activities.

Will be implemented by the framework.
dotnet/orleans#2428

from orleans.activities.