You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/01/26 14:32:00 UTC
[jira] [Resolved] (IGNITE-14414) Cluster initialization flow
[ https://issues.apache.org/jira/browse/IGNITE-14414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin resolved IGNITE-14414.
------------------------------------------
Resolution: Won't Fix
This ticket should be revised in the context of https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=186876642
> Cluster initialization flow
> ---------------------------
>
> Key: IGNITE-14414
> URL: https://issues.apache.org/jira/browse/IGNITE-14414
> Project: Ignite
> Issue Type: New Feature
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> For a cluster to become operational, the metastorage instance must be initialized first. The initialization command chooses a set of nodes (normally, 3 - 5 nodes) to host the distributed metastorage Raft group. When a node receives the initialization command, it either creates a bootstrapped Raft instance with the given members (if this is a metastorage group node), or writes the metastorage group member IDs to the vault as a private system-level property.
> After the metastorage is initialized, components start to receive and process watch events, updating the local state according to the changes received from the watch.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)