[
https://issues.apache.org/jira/browse/IGNITE-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-23754:
---------------------------------------
Summary: Do not fail initialized node start due to CMG or MG unavailability
(was: Do not fail initialized node join due to CMG or MG unavailability)
> Do not fail initialized node start due to CMG or MG unavailability
> ------------------------------------------------------------------
>
> Key: IGNITE-23754
> URL: https://issues.apache.org/jira/browse/IGNITE-23754
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> When an initialized node starts, it tries to join the cluster. If the CMG is
> not available, the join is not possible. The node will then try to join for
> 10 seconds and then it will fail its startup.
> This behavior is wrong because (given the CMG has replication factor more
> than 1), if we start nodes one by one with intervals of more 10 seconds, none
> of them will be able to fully start.
> {*}Definition of done{*}: during its start, an initialized node must attempt
> to join the cluster for an unlimited period of time so that unavailability of
> CMG or MG doesn't make it fail its startup sequence.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
