On Tue, Mar 7, 2017 at 1:26 AM, Alexey Goncharuk <alexey.goncha...@gmail.com > wrote:
> Guys, > > I was looking at this ticket and have a question related to the lock > semantics: > > Suppose I have a node which has already acquired the lock, and then all > affinity nodes related to the lock leave topology. In this case, if we > automatically re-created the lock, we would end up having two lock owners > in the grid, which is unacceptable. > > I think throwing an exception and forcing a user to re-create the lock by > himself is a correct way to resolve this. > Which user operation would result in exception? To my knowledge, user may already be holding the lock and not invoking any Ignite APIs, no?
