[jira] [Commented] (IGNITE-6890) General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor)
[ https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717073#comment-16717073 ] ASF GitHub Bot commented on IGNITE-6890: Github user anton-vinogradov closed the pull request 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 should be handled using common approach. IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > introduces {{FailureHandler}} interface and describes all failures that > should be treated as critical. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6890) General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor)
[ https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16417305#comment-16417305 ] ASF GitHub Bot commented on IGNITE-6890: GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3712 IGNITE-6890: iep-14 implementation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-6890-iep14 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3712.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3712 commit c3a99150c658314e62003850045e76f72b380d46 Author: Dmitriy SorokinDate: 2018-03-28T13:03:27Z IGNITE-6890: iep-14 implementation. > 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 should be handled using common approach. IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > introduces {{FailureHandler}} interface and describes all failures that > should be treated as critical. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6890) General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor)
[ https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372776#comment-16372776 ] Anton Vinogradov commented on IGNITE-6890: -- [~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)
[jira] [Commented] (IGNITE-6890) General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor)
[ https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372774#comment-16372774 ] ASF GitHub Bot commented on IGNITE-6890: GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3558 IGNITE-6890 General way for handling Ignite failures (NodeInvalidator… … should be replaced with IgniteFailureProcessor) Signed-off-by: Anton VinogradovYou can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6890 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3558.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3558 commit 4730f6c7511a715789fcf2ac1139f3c1526e7d19 Author: Anton Vinogradov Date: 2018-02-22T12:58:35Z IGNITE-6890 General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor) Signed-off-by: Anton Vinogradov > 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)