You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2021/03/04 14:40:00 UTC

[jira] [Updated] (IGNITE-14231) IGNITE_ENABLE_FORCIBLE_NODE_KILL flag is not supported in inverse connection request scenario

     [ https://issues.apache.org/jira/browse/IGNITE-14231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Chugunov updated IGNITE-14231:
-------------------------------------
    Release Note: Support for IGNITE_ENABLE_FORCIBLE_NODE_KILL flag in inverse connection protocol added

> IGNITE_ENABLE_FORCIBLE_NODE_KILL flag is not supported in inverse connection request scenario
> ---------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-14231
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14231
>             Project: Ignite
>          Issue Type: Bug
>          Components: networking
>    Affects Versions: 2.9.1
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Major
>             Fix For: 2.11
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> IGNITE_ENABLE_FORCIBLE_NODE_KILL flag enables server nodes to forcibly kill clients visible via Discovery but unreachable by Communication protocol.
> This leads to infinite loops when server tries to establish communication connection to unreachable client fails and tries again effectively ignoring the flag.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)