Ensure ZooKeeper Orphan Node Cleanup Is Configured

低等級 1人工審核tdsql

說明

TDSQL creates many task/alert/state ZNodes in ZooKeeper. Abnormal exits or network jitter can produce orphan nodes, and long-term accumulation causes: ZK memory bloat, affecting overall availability Residual alert/task nodes leaking historical sensitive information Historical credential/password fields remaining readable long-term TDSQL provides two cleanup mechanisms: <clear_zknode value="15"/> - cleans up ordinary ...

檢查方式

稽核方法: 人工審核

此項建議無法自動檢查。當您傳入 --include-manual 時，掃描結果會列出此項目並附帶這些說明。

# Check scheduler.xml grep -E '(clear_zknode|alarm_zknode)' /path/to/tdsql/conf/scheduler.xml # Check for residual historical nodes in ZK (should not exceed recent counts) zkCli.sh -server <zk_ip>:<port> ls /tdsql/job ls /tdsql/alarm

修補方式

修補方法: 操作指南或基礎設施修補檔

<clear_zknode value="15"/>  <alarm_zknode open_clear="1" expire_time="86400" check_interval="3600"/>

屬性

作業系統: 不限
標籤: tdsqlzookeeper
參考資料: CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 12.7 Ensure ZooKeeper Orphan Node Cleanup Is Configured