I fixed this issue with not release locks (
https://issues.apache.org/jira/browse/IGNITE-2008), fix will be available
in 1.5 release.
On Thu, Dec 3, 2015 at 9:28 AM, Dmitriy Setrakyan
wrote:
> Thanks Semyon!
>
> On Wed, Dec 2, 2015 at 10:13 PM, Semyon Boikov
> wrote:
>
> > Dmitry, Valentin,
>
Thanks Semyon!
On Wed, Dec 2, 2015 at 10:13 PM, Semyon Boikov wrote:
> Dmitry, Valentin,
>
> I'll look at this issue today.
>
> On Thu, Dec 3, 2015 at 6:26 AM, Dmitriy Setrakyan
> wrote:
>
> > Val,
> >
> > I think if lock futures are not complete, then the issue remains, because
> > it can caus
Dmitry, Valentin,
I'll look at this issue today.
On Thu, Dec 3, 2015 at 6:26 AM, Dmitriy Setrakyan
wrote:
> Val,
>
> I think if lock futures are not complete, then the issue remains, because
> it can cause hanging clients. Did you get an idea of what it would take to
> fix it?
>
> D.
>
> On Wed
Val,
I think if lock futures are not complete, then the issue remains, because
it can cause hanging clients. Did you get an idea of what it would take to
fix it?
D.
On Wed, Dec 2, 2015 at 7:25 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> I played with this and it seems that
I played with this and it seems that locks are actually released when node
leaves, but lock futures that are waiting for this lock are never
completed. Therefore, this issue can be workarounded by replacing lock()
method with tryLock() in a loop.
Anyone knows why this can happen?
-Val
On Wed, De
Igniters,
Does anyone know the severity of this issue? In which cases is it
reproduced?
https://issues.apache.org/jira/browse/IGNITE-2008
In my view, we already have support for it, so it should be just a bug.
Anyone knows how hard it is to fix?
D.
