yugabyte/yugabyte-db

Zero out hybrid time below history retention on major compactions

Open

#10,024 opened on Sep 16, 2021

View on GitHub
 (1 comment) (0 reactions) (1 assignee)C (1,003 forks)batch import
area/docdbgood first issuekind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-742 Recently mentioned by @spolitov.

This will help with space savings.

Contributor guide

Research direction
Study the hybrid time implementation, history retention mechanism, and major compaction logic in YugabyteDB. Identify where hybrid time can be zeroed safely without affecting correctness.
Tech stack
c
Domain
backenddatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
CDatabase internalsCompaction algorithms
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15