[jira] [Comment Edited] (IGNITE-17592) Fix synchronous await on futures in raft group events rebalance listener

["Kirill Gusakov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-17592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632361#comment-17632361 ] 

Kirill Gusakov edited comment on IGNITE-17592 at 11/11/22 1:49 PM:
-------------------------------------------------------------------

It looks like we can replace these gets by
 * futures chain
 * return the result future from RebalanceRaftGroupEventsListener#onNewPeersConfigurationApplied
 * push this future to NodeImpl.getOptions().getCommonExecutor() for async execution

But we should return to this issue, only if this place will not be removed at all after IGNITE-18060


was (Author: kgusakov):
It looks like we can replace these gets by
 * futures chain
 * return the result future from RebalanceRaftGroupEventsListener#onNewPeersConfigurationApplied
 * push this future to NodeImpl.getOptions().getCommonExecutor() for async execution

But we should to return to this issue, only if this place will not be removed at all after IGNITE-18060

> Fix synchronous await on futures in raft group events rebalance listener
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-17592
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17592
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Semyon Danilov
>            Assignee: Kirill Gusakov
>            Priority: Major
>              Labels: ignite-3
>
> Raft group events listener should not be blocked by Future#get methods as it can move the system to the unstable state. 
> See the TODOs with this ticket in the source code of RebalanceRaftGroupEventsListener.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)