pingcap/tidb

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

Open

Aperta il 13 mar 2024

Vedi su GitHub
 (1 commento) (0 reazioni) (0 assegnatari)Go (40.090 star) (6186 fork)batch import
affects-8.1good first issueseverity/moderatesig/sql-infratype/bug

Descrizione

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

Guida contributor

Tech stack
gosql
Dominio
backenddatabase
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Go programmingSQL basicsTiDB configuration system
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
70
Direzione di ricerca
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.