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

Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2021/08/12 12:19:00 UTC

[jira] [Updated] (IGNITE-15272) Raft group not being able to refresh leader

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

Semyon Danilov updated IGNITE-15272:
------------------------------------
    Description: If a raft group is being started within a message handler the cluster will hang forever, as the raft group service constructor is sending a RefreshLeader request and waits on the response future while netty thread, managing the connection, as well as Project Reactor's DirectProcessor won't be able to process the response . We need to make this operation asynchronous.

> Raft group not being able to refresh leader
> -------------------------------------------
>
>                 Key: IGNITE-15272
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15272
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Semyon Danilov
>            Assignee: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>
> If a raft group is being started within a message handler the cluster will hang forever, as the raft group service constructor is sending a RefreshLeader request and waits on the response future while netty thread, managing the connection, as well as Project Reactor's DirectProcessor won't be able to process the response . We need to make this operation asynchronous.



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