Cop task's backoff time is not appropriate in execution summary #58703
Labels
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.5
This bug affects the 8.5.x(LTS) versions.
severity/minor
type/bug
The issue is confirmed as a bug.
In current tidb code, the cop task's backoff time in execution summary is not correctly calculated:
tidb/pkg/distsql/select_result.go
Line 658 in 4f78f12
The backoff time in selectResultRuntimeStats is replaced by the new CopRuntimeStats's backoff time when their backoff keys are the same. It is more reasonable to sum the backoff values up here.
Currently, the accurate backoff info can be found in the slow log item if the query is regarded as a slow query.
The text was updated successfully, but these errors were encountered: