You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
set schedule.max-pending-peer-count as uint64(math.MaxInt32)
What did you expect to see?
parse value success
What did you see instead?
[2024/03/25 06:55:50.799 +00:00] [WARN] [persist_options.go:887] ["failed to parse schedule.max-pending-peer-count from PersistOptions's ttl storage"] [error="strconv.ParseUint: parsing \"2.147483647e+09\": invalid syntax"]
and get default value
Error Stack
json unmarshal will convert number(such as uint64(math.MaxInt32)) to float64
Bug Report
What did you do?
set
schedule.max-pending-peer-count
asuint64(math.MaxInt32)
What did you expect to see?
parse value success
What did you see instead?
[2024/03/25 06:55:50.799 +00:00] [WARN] [persist_options.go:887] ["failed to parse schedule.max-pending-peer-count from PersistOptions's ttl storage"] [error="strconv.ParseUint: parsing \"2.147483647e+09\": invalid syntax"]
and get default value
Error Stack
json unmarshal will convert number(such as
uint64(math.MaxInt32)
) to float64and then set float64 into TTL config
pd/server/server.go
Line 1955 in 6ee25f9
will transfer
fmt.Sprint(math.MaxInt32)
to2.147483647e+09
which will meet error[2024/03/25 06:55:50.799 +00:00] [WARN] [persist_options.go:887] ["failed to parse schedule.max-pending-peer-count from PersistOptions's ttl storage"] [error="strconv.ParseUint: parsing \"2.147483647e+09\": invalid syntax"]
What version of PD are you using (
pd-server -V
)?master
The text was updated successfully, but these errors were encountered: