pingcap/tidb

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

Open

#14,760 建立於 2020年2月13日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Go (40,090 star) (6,186 fork)batch import
help wantedsig/sql-infratype/enhancement

描述

Feature Request

Is your feature request related to a problem? Please describe:

If TiDB in a cluster has different DDL leases, the schemas between TiDB may be out of sync.

Describe the feature you'd like:

It is best to verify that the DDL leases of all TiDBs in the cluster are consistent.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

貢獻者指南

技術棧
go
領域
databaseinfrastructure
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TiDB DDL internalsGo programmingDistributed systems
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
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.