[tidb-x] add index blocked after simulated s3 network partition or latency

[Lily2025]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

1、enable global sort and dxf
2、run sysbench
3、add index for one table
4、simulated s3 network partition or latency last for 3mins
5、recovery fault

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

add index can succeed after fault recover

3. What did you see instead (Required)

add index blocked after simulated s3 network partition or latency (the state is always running)

tidb (8).log.zip

4. What is your TiDB version? (Required)

./tidb-server -V
Release Version: v9.0.0-beta.2.pre-977-gcf4647e
Edition: Enterprise
Git Commit Hash: cf4647e
Git Branch: HEAD
UTC Build Time: 2025-12-29 13:20:09
GoVersion: go1.25.5
Race Enabled: false
Check Table Before Drop: false
Store: unistore
Enterprise Extension Commit Hash: dc633aae52eb11b4e3549e3a7ef5b0ed14e159b1
Kernel Type: Next Generation
2025-12-30T07:04:31.787+0800

[Lily2025]

/severity critical
/assign D3Hunter

[Lily2025]

/remove-severity critical
/severity major

[Lily2025]

/assign gmhdbjd