lablup/raftify

Implement snapshot creation policy

Open

#48 opened on Oct 17, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (14 forks)auto 404
featuregood first issueimprovementsnapshot

Repository metrics

Stars
 (45 stars)
PR merge metrics
 (PR metrics pending)

Description

The current implementation of creating a snapshot is only executed after handle_committed_normal_entry.

I think there could be better ways.

For example, we can implement the following policies:

Create a snapshot when the size of the FSM exceeds a specific threshold. Generate a snapshot when the number of log entries surpasses a certain count.

Note: snapshot contains several metadata configuring the cluster, so wrong implementation of this would break the consistency of the raft loop.

Contributor guide

Research direction
Study the existing snapshot creation logic in handle committed normal entry and the snapshot metadata structure. Then design policies based on FSM size or log entry count, ensuring consistency with the Raft loop.
Tech stack
rust
Domain
distributed systemsbackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustRaftDistributed Systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30