autoid service rebase internal SQL should not meet transaction conflict #50819
Labels
affects-6.4
affects-6.5
affects-7.0
affects-7.1
affects-7.2
affects-7.3
affects-7.4
affects-7.5
affects-7.6
fixes-7.5.1
fixes-8.0
report/customer
Customers have encountered this bug.
severity/minor
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
As the title says, there should be only one autoid service leader visiting the autoid meta key,
and that operation should be under lock protect, so there should never be a transaction conflict.
But from the log, I see the autoid been increased twice, get transaction conflict, result in "hole" in the id sequence.
The text was updated successfully, but these errors were encountered: