select with limit cost exceed 40s but explain analyze only 100ms

[lzmhhh123]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

load tpch_10 and create TiFlash replica for each table.

execute select * from lineitem limit 100

2. What did you expect to see? (Required)

SQL finished in a very short time.

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

v4.0.5

5. W/A (Workaround)

use tikv instead tiflash.

6. Affected versions

v4.0.5

7. Fixed versions

v4.0.7

[sre-bot]

Integrity check:
component severity RCA symptom affect_version fix_version fields are empty

Please comment /info to get template

[seiya-annie]

/info

[ti-srebot]

Please edit this comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added

1. Root Cause Analysis (RCA)

	// Because in rpc logic, context.Cancel() will be transferred to rpcContext.Cancel error. For rpcContext cancel,
	// we need to retry the request. But for context cancel active, for example, limitExec gets the required rows,
	// we shouldn't retry the request, it will go to backoff and hang in retry logic.

2. Symptom

see in bug body

3. All Trigger Conditions

see in the Minimal reproduce step (Required)

4. Workaround (optional)

use tikv instead tiflash.

5. Affected versions

[v4.0.5:4.0.5]

6. Fixed versions

v4.0.7

[lysu]

TiKV also became slow if user disables Superbatch(tikv-client.max-batch-size == 0)

it was introduced by 4.0.5 #18580

[seiya-annie]

add component/tikv label based on labels in PR