import into failed after injection ddl owner network partition

[Lily2025]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

1、import into
2、injection ddl owner network partition
3、import into failed

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

import into succeed

3. What did you see instead (Required)

import into failed

[2025-01-08 18:13:02] ###### start import into
[2025/01/08 18:14:01.469 +08:00] injection ddl owner network partition lasts for 3mins
[2025/01/08 18:17:01.471 +08:00] recover fault
[2025-01-08 18:18:02] import into failed

task-id=120007

tidb-0.log.zip
tidb-1.log.zip

4. What is your TiDB version? (Required)

./tidb-server -V
Release Version: v9.0.0-alpha-65-gd1ed962
Edition: Community
Git Commit Hash: d1ed962
Git Branch: HEAD
UTC Build Time: 2025-01-08 06:04:38
GoVersion: go1.23.4
Race Enabled: false
Check Table Before Drop: false
Store: unistore
2025-01-08T18:12:54.336+0800

[Lily2025]

/severity major
/assign lance6716
/remove-type bug

[Lily2025]

/type bug

[lance6716]

caused by DXF framework canceled the subtask

[2025/01/08 18:17:09.906 +08:00] [INFO] [task_executor.go:143] ["subtask is scheduled away, cancel running"] [task-id=120007] [task-type=ImportInto] [subtaskID=150067]

[Lily2025]

/assign cbcwestwolf

[D3Hunter]

introduced by #58615
the pr introduced subtask context, but if subtaskCtx is cancelled due to subtask scheduled away, our markSubTaskCanceledOrFailed is still using step context to check whether the subtask is cancelled or we want to cancel the running of the subtask, cause task executor thinks that the subtask has failed with context cancelled error