yugabyte/yugabyte-db

Do not dump "orphaned replicates" (uncommitted Raft records) on tablet bootstrap

Open

#235 opened on Apr 23, 2018

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

Description

Jira Link: DB-1666

  • There could be a lot of these records.
  • Values could be large.
  • There could be sensitive customer data that could later be uploaded for log analysis.

Contributor guide

Tech stack
c
Domain
databasesecurity
Issue type
security
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Raft consensus algorithmYugabyteDB architectureC programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the tablet bootstrap process in the YugabyteDB codebase. Look for where Raft records are dumped or logged during bootstrap. Identify the code path that ingests uncommitted Raft entries and determine how to suppress logging of such records. Consider the impact on debugging and diagnostics. Possibly modify the logging to exclude 'orphaned' records or ensure they are not dumped as part of standard bootstrap logs.
Do not dump "orphaned replicates" (uncommitted Raft records) on tablet bootstrap · yugabyte/yugabyte-db#235 | Good First Issue