You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2024/07/03 13:17:00 UTC

[jira] [Assigned] (IGNITE-22633) Catalog compaction. Choosing coordinator.

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

Konstantin Orlov reassigned IGNITE-22633:
-----------------------------------------

    Assignee: Konstantin Orlov

> Catalog compaction. Choosing coordinator.
> -----------------------------------------
>
>                 Key: IGNITE-22633
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22633
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Pavel Pereslegin
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> By design, catalog compaction should only be performed by the coordinator node.
> Catalog compaction coordinator is the same node as the metastorage group leader.
> Basically, we need to implement logic (as part of the CatalogManager) that will listen the metastorage leader election (MetaStorageLeaderElectionListener?) and toggle an internal flag that will indicate that the current node can initiate the catalog compaction procedure.



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