pingcap/tidb

Mismatch unit of configuration item when set and then get config via SQL

Open

#51,740 建立於 2024年3月13日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Go (40,090 star) (6,186 fork)batch import
affects-8.1good first issueseverity/moderatesig/sql-infratype/bug

描述

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

set config tikv `raftstore.raft-entry-max-size`='24MB';

show config where type='tikv' and name ='raftstore.raft-entry-max-size';

2. What did you expect to see? (Required)

The output value should be consistent with the input '24MB';

3. What did you see instead (Required)

'24MiB'. In other words, MiB vs MB.

4. What is your TiDB version? (Required)

v7.5.1

貢獻者指南

技術棧
gosql
領域
backenddatabase
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingSQL basicsTiDB configuration system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Investigate the SQL layer handling of config set/show commands. Look at how the unit string is parsed and converted internally. The issue likely lies in the conversion between user input (MB) and internal representation (MiB). Focus on files related to configuration parsing and SQL execution for config statements. Check if there is a unit normalization step that incorrectly converts MB to MiB.