You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2025/06/06 07:22:00 UTC
[jira] [Assigned] (IGNITE-25567) Node start dependent on COLOCATION_FEATURE_FLAG
[ https://issues.apache.org/jira/browse/IGNITE-25567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy reassigned IGNITE-25567:
------------------------------------------
Assignee: Roman Puchkovskiy
> Node start dependent on COLOCATION_FEATURE_FLAG
> ------------------------------------------------
>
> Key: IGNITE-25567
> URL: https://issues.apache.org/jira/browse/IGNITE-25567
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> Following logic is expected to be implemented.
> * If the node is started on top of non-colocation PDS, it should ignore COLOCATION_FEATURE_FLAG and start in non-colocation mode.
> * If the node is started on top of colocation PDS, it should ignore COLOCATION_FEATURE_FLAG and start in colocation mode.
> * If it's new node startup, it should start in the COLOCATION_FEATURE_FLAG mode.
> h3. Implementation Notes
> If it's not trivial to analyse actual PDS, me may use following vault-based approach.
> * On first startup node writes colocation mode to vault.
> * On every start node reads colocation mode from vault, if there's no one - that mean that it's non-colocation mode. Otherwise node starts in corresponding mode specified in vault.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)