You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "slava.koptilin" <sl...@gmail.com> on 2017/09/05 14:41:37 UTC

Re: ignite.active(true) blocking forever

Hi,

I am sorry for the delay.

I was able to reproduce this issue, and it looks like a bug.
I created a jira ticket in order to track this
https://issues.apache.org/jira/browse/IGNITE-6274

Thanks,
Slava.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite.active(true) blocking forever

Posted by Yakov Zhdanov <yz...@apache.org>.
Then you may have a data loss?

--Yakov

2017-09-06 12:51 GMT+03:00 Вячеслав Коптилин <sl...@gmail.com>:

> Hi Yakov,
>
> At first sight, it seems that we can use the same approach for this issue,
> but in this particular case, I think, the best way to handle
> OutOfMemoryError is to shutdown the node that could not be activated.
>
> Best regards,
> Slava.
>
> 2017-09-06 11:26 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
>
>> Slava, this looks like the issue with start cache operation throwing
>> exception on some nodes and cache start rollback. I remember you
>> implemented that fix. Can we apply the same machinery to rollback the
>> activation with proper exception?
>>
>> --Yakov
>>
>
>

Re: ignite.active(true) blocking forever

Posted by Вячеслав Коптилин <sl...@gmail.com>.
Hi Yakov,

At first sight, it seems that we can use the same approach for this issue,
but in this particular case, I think, the best way to handle
OutOfMemoryError is to shutdown the node that could not be activated.

Best regards,
Slava.

2017-09-06 11:26 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:

> Slava, this looks like the issue with start cache operation throwing
> exception on some nodes and cache start rollback. I remember you
> implemented that fix. Can we apply the same machinery to rollback the
> activation with proper exception?
>
> --Yakov
>

Re: ignite.active(true) blocking forever

Posted by Yakov Zhdanov <yz...@apache.org>.
Slava, this looks like the issue with start cache operation throwing
exception on some nodes and cache start rollback. I remember you
implemented that fix. Can we apply the same machinery to rollback the
activation with proper exception?

--Yakov