apple / apple/foundationdb

Use the minimum stopped version as the known committed version if all logs have responded

Open
#312 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
16.7k
Forks
1.6k
Avg merge
1d 20h
Merged PRs (30d)
126

Description

This is an optimization to copy less data during recoveries. We have to copy all versions between the known committed version and the recovery version before accepting new commits. Therefore in the special case that no logs have failed, we do not have to copy any data, because we know the recovery version is available on all of the old logs.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by tracing recovery handling and how the known committed version and minimum stopped version are calculated; done means the no-failed-log case avoids unnecessary data copying while preserving recovery correctness.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.