yugabyte/yugabyte-db

[DocDB] add is_yb_managed gflag to master and TServers

Open

#30,110 建立於 2026年1月26日

在 GitHub 查看
 (0 留言) (0 反應) (1 負責人)C (8,229 star) (1,003 fork)batch import
area/docdbgood first issuekind/enhancementpriority/medium

描述

Jira Link: DB-19966

Description

Plan is to pass this flag with a value of true for instances running in YBM. That is, the code that starts these processes on YBM will set this flag to true.

Flag should default to false.

For now, nothing will be reading this flag. We plan to use this flag to roll out some features to YBM first and only later to YBA/OSS.

Probably want to put this in common_flags.h or the equivalent

(We need the flag defined first before YBM can start passing it.)

backport this to 2024.2, 2025.1, 2025.2

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

貢獻者指南

技術棧
cpp
領域
database
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C++ knowledgegflags familiarityYugabyteDB codebase basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Examine the pattern for defining gflags in common flags.h (likely in src/yb/common/common flags.h). Add a new gflag called 'is yb managed' with default false. Ensure it is accessible from both master and TServer processes. No code should read this flag yet; only define it. Consult existing gflag definitions for proper registration and declaration. The backporting to specific versions can be addressed after the initial implementation.