yugabyte/yugabyte-db

[DocDB] GetConsensusState could also return current index.

Open

#13,702 opened on Aug 21, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)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-3242

Description

GetConsensusState is used by scripts such as yugatool to generate tablet-reports.

However the information printed wrt term/index are inaccurate:

The index printed which comes from RaftConfigPB corresponds to the index at which the last config-change took place.

It would be more relevant to have the current-index information be added to the proto. Also, for the leader, it would be useful to add information about whether or not the initial no-op has been replicated.

cc : @tvesely @eugeneckim @tylarb

Contributor guide

Research direction
Investigate the current GetConsensusState proto definition and trace how term/index are obtained from RaftConfigPB. Modify the proto to include current index field and leader no op flag. Ensure backward compatibility.
Tech stack
c
Domain
backend
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.
Half day
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.
Mostly clear
Prerequisites
CProtobufRaft
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40