Verify that the DDL leases of all TiDBs in the cluster are consistent

Description

Contributor guide

Tech stack

go

Domain

databaseinfrastructure

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

5

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.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

TiDB DDL internalsGo programmingDistributed systems

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

10

Research direction

This issue asks for a verification mechanism to ensure DDL leases are consistent across TiDB cluster. To start, examine the DDL module in the TiDB codebase, particularly how lease settings are configured and propagated. Look for existing cluster consistency checks (e.g., via etcd or similar). Propose a design for a check that compares lease values (e.g., during startup or health check). Consider implementing a CLI tool or a built in diagnostic endpoint. No existing PRs or comments provide further guidance.