[jira] [Assigned] (IGNITE-16034) Unblock a node start that happenes before Metastorage is ready

["Aleksandr Polovtcev (Jira)" <ji...@apache.org>]

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

Aleksandr Polovtcev reassigned IGNITE-16034:
--------------------------------------------

    Assignee: Aleksandr Polovtcev

> Unblock a node start that happenes before Metastorage is ready
> --------------------------------------------------------------
>
>                 Key: IGNITE-16034
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16034
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> All tests that are passing today start a Metastorage in the first node, others started when it is fully started. But in real life, we have no of this guarantee.
> Nodes try to start in arbitrary order, and it will be a bad result when part of them fails with message:
> {noformat}
> Cannot start meta storage manager because there is no node in the cluster that hosts meta storage.
> {noformat}
> The behavior is demonstrated in _ItIgniteNodeRestartTest#testTwoNodesRestartReverse_



--
This message was sent by Atlassian Jira
(v8.20.1#820001)