You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Polovtsev (Jira)" <ji...@apache.org> on 2025/02/14 16:13:00 UTC
[jira] [Updated] (IGNITE-24517) Persistent Raft meta for empty zones
[ https://issues.apache.org/jira/browse/IGNITE-24517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Polovtsev updated IGNITE-24517:
-----------------------------------------
Description:
Zone-wide Raft listener dispatches the received commands to Table-wide "listeners" each of which operates its own table-partition storage. Therefore, zone-wide Raft listener doesn't have a persistent state of its own. This is a problem for zones without tables, because some data (like committed configuration and lease information) is expected to be persisted but without table-partition storages, it is not saved anywhere.
It is proposed to save this information into the TX state storage and use it as a persistent store if no partition stores are present.
> Persistent Raft meta for empty zones
> ------------------------------------
>
> Key: IGNITE-24517
> URL: https://issues.apache.org/jira/browse/IGNITE-24517
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
>
> Zone-wide Raft listener dispatches the received commands to Table-wide "listeners" each of which operates its own table-partition storage. Therefore, zone-wide Raft listener doesn't have a persistent state of its own. This is a problem for zones without tables, because some data (like committed configuration and lease information) is expected to be persisted but without table-partition storages, it is not saved anywhere.
> It is proposed to save this information into the TX state storage and use it as a persistent store if no partition stores are present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)