[ https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372776#comment-16372776 ]
Anton Vinogradov edited comment on IGNITE-6890 at 2/22/18 1:02 PM: ------------------------------------------------------------------- [~cyberdemon], I did some refactoring on your changes, please see result at https://github.com/apache/ignite/pull/3558 Origninal PR adress is https://github.com/apache/ignite/pull/3083 was (Author: avinogradov): [~cyberdemon], I did some refactoring on your changes, please see result at https://github.com/apache/ignite/pull/3558 > General way for handling Ignite failures (NodeInvalidator should be replaced > with IgniteFailureProcessor) > --------------------------------------------------------------------------------------------------------- > > Key: IGNITE-6890 > URL: https://issues.apache.org/jira/browse/IGNITE-6890 > Project: Ignite > Issue Type: Improvement > Reporter: Anton Vinogradov > Assignee: Dmitriy Sorokin > Priority: Major > Labels: iep-14 > Fix For: 2.5 > > > Ignite failures which should be handled are: > # Topology segmentation; > # Exchange worker stop; > # Errors currently covered by NodeInvalidator. > Proper behavior should be selected according to result of calling > IgniteFailureHandler instance, custom implementation of which can be provided > in IgniteConfiguration. It can be node stop, restart or nothing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)