Hi, Can someone please help me out with following questions.
1) If the ignite is capable of detecting nodes segmentation and taking STOP,RESTART_JVM or NOOP action based on configured failure handlers then why do we need explicit SegmentationResolvers? 2) Does ignite always treat node segmentation as "Critical system error" and use "StopNodeOrHaltFailureHandler" to take required action which "Teminate Node"? 3) Are there any other reasons for "Critical system error detected" message? Thanks, Prasad On Wed, Nov 27, 2019 at 11:01 PM akurbanov <antkr....@gmail.com> wrote: > Hello, > > Please refer to documentation on failure handler: > https://apacheignite.readme.io/docs/critical-failures-handling. > > As it is correctly stated, we cannot restart the JVM without external > tooling, by default we are doing this for nodes that were started with > ignite.sh/bat so that Ignite start goes through > > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/startup/cmdline/CommandLineStartup.java > > As for the segmentation, subscribe to > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/events/EventType.html#EVT_NODE_SEGMENTED > > Event listeners doc: https://apacheignite.readme.io/docs/events > > You will receive this event in the listener and after this you might do > anything that you want with the JVM, easiest way is to exit JVM with some > code and handle it outside of the application. > > Best regards, > Anton > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
