Hello!
You can have your own failureHandler set, so I think.
Regards,
--
Ilya Kasnacheev
вт, 29 янв. 2019 г. в 19:52, wangsan :
> Thanks!
> The IgniteConfiguration.segmentationPolicy RESTART_JVM would be a little
> misleading. Exit java with some exit code ,The java application will ignore
Thanks!
The IgniteConfiguration.segmentationPolicy RESTART_JVM would be a little
misleading. Exit java with some exit code ,The java application will ignore
the exit code.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
It will use IgniteConfiguration.segmentationPolicy.
You can just try setting it to RESTART_JVM.
Regards,
--
Ilya Kasnacheev
вт, 27 нояб. 2018 г. в 17:18, wangsan :
> Can I use LifecycleEventType.AFTER_NODE_STOP to stop jvm? if segment event
> happens?
>
>
>
> --
> Sent from:
Can I use LifecycleEventType.AFTER_NODE_STOP to stop jvm? if segment event
happens?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Can I config the FailureHandler when segment error happen?
The IgniteConfiguration FailureHandler only used on other exception(error)
happens?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
, wangsan :
> Why GridDiscoveryManager onSegmentation use StopNodeFailureHandler?
> But not the StopNodeOrHaltFailureHandler !
> In my case,when net problem happen, I wan't the jvm close?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Why GridDiscoveryManager onSegmentation use StopNodeFailureHandler?
But not the StopNodeOrHaltFailureHandler !
In my case,when net problem happen, I wan't the jvm close?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
