ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: IEP-14: Ignite failures handling (Discussion)
Date Thu, 15 Mar 2018 01:12:49 GMT
On Tue, Mar 13, 2018 at 11:17 PM, Nick Pordash <nickpordash@gmail.com>

> I can tell you as a user that if any library I was using in my application
> called System.exit without my consent would result in a lot of frustration.
> If ignite enters an unrecoverable state then I think that is something that
> should be observable locally, similar to node segmentation and then the
> application can decide the best course of action.

Nick, you would be a lot more frustrated if Ignite was frozen and every
call to Ignite would freeze the application threads as well. Again, if you
prefer to keep the process around, even if Ignite freezes, then you can
always configure this behavior, but I still believe that the default should
be to kill the process.

Ignite is a horizontally scalable system, so killing of one node should not
be a significant event and should not disrupt the cluster. However, a
freeze of one node is a significant event and can bring the whole cluster
to a halt.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message