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.
Mismatch unit of configuration item when set and then get config via SQL · pingcap/tidb#51740 | Good First Issue