cloud_storage/scrubbing: self-healing

Open
#15,034 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start with the cloud_storage/scrubbing subsystem and review how the scrubber currently reports anomalies. Define the scope and completion criteria for re-uploading missing segments and patching gaps before considering spillover manifests or offset anomalies.

Written by the indexing model from the issue text.

Description

area/cloud-storage kind/enhance

Currently, the scrubber only does reporting of anomalies. This is valuable since it informs the assumptions which we can use during development and bubbles up issues before customers run into them. However, the scrubber could be extended with self-healing capabilities. The most useful (and straightforward) self healing capability is the re-upload of missing segments and the patching up of gaps.

Other types of self-healing include the re-upload of missing spillover manifests and correcting various offset anomalies (e.g. incorrect deltas, etc).

JIRA Link: CORE-1585

Dominant language
C++
Stars
12.6k
Forks
792
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redpanda-data/redpanda

All issues in redpanda-data/redpanda

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.