[
https://issues.apache.org/jira/browse/IGNITE-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov resolved IGNITE-17253.
------------------------------------
Resolution: Won't Fix
After careful examination of how RAFT does snapshots, it became clear that
transmission mechanism is up to to implementation. Overall design is vague
enough to avoid any folders creation. Main structure of classes is implemented
in IGNITE-17083
> Support for snapshot streaming in RAFT state machine
> ----------------------------------------------------
>
> Key: IGNITE-17253
> URL: https://issues.apache.org/jira/browse/IGNITE-17253
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> In JRaft, snapshotting works through files: first, a snapshot is written to a
> file, later it is sent to follower(s).
> This requires additional FS space, and it is a bit strange for in-memory
> cases.
> We need to switch to streaming way of doing snapshots: when the leader needs
> to bootstrap a follower, it opens a 'channel' to the follower, starts
> producing a snapshot and streaming it to the follower. The follower applies
> the snapshot in the same streaming way.
> This ticket is about modifying JRaft internal infrastructure to switch to
> snapshot streaming.
> See IGNITE-17083
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
