[
https://issues.apache.org/jira/browse/IGNITE-17302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17302:
-------------------------------------
Description:
It's supposed that replication state machine (e.g. RaftGroupListener) will
handle multiple storages. For example PartitionListener will use:
* MvPartitionStorage - common multi-version partition storage for core
partition data.
* Both volatile and persistent lock storages IGNITE-15932.
* Persistent storage for txn state IGNITE-15931.
* Index storages.
Generally speaking replication logic is decoupled from data-storages, and there
are only few intersection points:
* raft log truncation -
was:
It's supposed that replication state machine (e.g. RaftGroupListener) will
handle multiple storages. For example PartitionListener will use
* MvPartitionStorage - common multi-version partition storage for core
partition data.
* Both volatile and persistent lock storages IGNITE-15932.
* Persistent storage for txn state
[IGNITE-15931|https://issues.apache.org/jira/browse/IGNITE-15931].
> Raft listener multi-storage support
> ------------------------------------
>
> Key: IGNITE-17302
> URL: https://issues.apache.org/jira/browse/IGNITE-17302
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3, transaction3_rw
>
> It's supposed that replication state machine (e.g. RaftGroupListener) will
> handle multiple storages. For example PartitionListener will use:
> * MvPartitionStorage - common multi-version partition storage for core
> partition data.
> * Both volatile and persistent lock storages IGNITE-15932.
> * Persistent storage for txn state IGNITE-15931.
> * Index storages.
> Generally speaking replication logic is decoupled from data-storages, and
> there are only few intersection points:
> * raft log truncation -
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
