[
https://issues.apache.org/jira/browse/IGNITE-22564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864696#comment-17864696
]
Kirill Sizov edited comment on IGNITE-22564 at 7/10/24 2:52 PM:
-----------------------------------------------------------------
Created a PR with the PoC of Raft decoupling.
[https://github.com/apache/ignite-3/pull/4005]
Now it's possible to host CMG and Metastore in separate dirs, though by default
they're placed inside node's working dir.
At the moment this change is not backward compatible with the existing schema.
Need more development to add backward compatibility.
was (Author: JIRAUSER301198):
Created a PR with the PoC of Raft decoupling. Now it's possible to host CMG and
Metastore in separate dirs, though by default they're placed inside node's
working dir.
At the moment this change is not backward compatible with the existing schema.
Need more development to add backward compatibility.
> Decouple metastore and CMG RAFT log from data partitions RAFT log
> -----------------------------------------------------------------
>
> Key: IGNITE-22564
> URL: https://issues.apache.org/jira/browse/IGNITE-22564
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Pligin
> Assignee: Kirill Sizov
> Priority: Major
> Labels: ignite-3
>
> Currently, RAFT logs for all subsystems are stored in subdirectories within
> the same working directory. During high load, Ignite may reach the disk I/O
> throughput limits. To mitigate this, splitting RAFT storage access across
> multiple disks can be beneficial.
> One solution is to separate the metadata (CMG and Metastore) RAFT logs from
> the data partitions RAFT logs, placing them on different disks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
