You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/06/30 08:18:00 UTC
[jira] [Commented] (IGNITE-17198) Minimal implementation of pure in-memory storage (with in-memory RAFT)
[ https://issues.apache.org/jira/browse/IGNITE-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560912#comment-17560912 ]
Roman Puchkovskiy commented on IGNITE-17198:
--------------------------------------------
Thank you for the review
> Minimal implementation of pure in-memory storage (with in-memory RAFT)
> ----------------------------------------------------------------------
>
> Key: IGNITE-17198
> URL: https://issues.apache.org/jira/browse/IGNITE-17198
> Project: Ignite
> Issue Type: New Feature
> Components: persistence
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> This is about the simpliest case possible: stable topology, nodes never leave, corner cases are not handled.
> What has to be done:
> # Volatile RAFT meta storage
> # Create volatile RAFT storages for a RAFT group (meta and logs) when RAFT group is about volatile storage; create persistent RAFT storages otherwise
> What does not need to be done:
> # Now, RAFT snapshots use files. We should not change this behavior in this task
--
This message was sent by Atlassian Jira
(v8.20.10#820010)