Re: Internal problems requiring graceful node shutdown, reboot, etc.

Igniters, I have implemented handling critical persistence I/O errors with temporary callback which stops the node. After PR merge the callback should be replaced with the generic solution proposed by Anton. Also I have added tests checking that node

Re: Internal problems requiring graceful node shutdown, reboot, etc.

Dmitry, Seems, we found that it's impossible to specify one action for all cases, but it's a good idea to allow user to decide what to do. We should make something like interface IgniteFailureHandler { IgniteFailureAction onFailure(IgniteFailureCause cause); } public enum IgniteFailureAction

Re: Internal problems requiring graceful node shutdown, reboot, etc.

HI Dmitry, I do not think it is good idea to mix failures of different threads into a single event type. - Practice shows that the most common source of problem is exchange thread - if disco worker has died, not will be excluded from topology safely - "nio-acceptor" can be spawn from multiple plac

Re: Internal problems requiring graceful node shutdown, reboot, etc.

Hi Dmitriy, I’m totally for the FailureProcessingPolicy addition to IgniteConfiguration. Apart of this, may I ask you to create corresponding documentation tickets for 2.4 release and “documentation” component? Only for the improvements that are getting into the next release. Basically you can

Internal problems requiring graceful node shutdown, reboot, etc.

Hi, Igniters! We have a set of internal problems, which required graceful node shutdown, or other reaction configured (See discussion thread http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Enhancement-Proposal-7-Internal-problems-detection-td24460.html ): - IgniteOutOfMemoryException