retry: enhance retry for ingestor on nextgen

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #61702

Problem Summary:

What changed and how does it work?

in nextgen, we are calling http api to do write and ingest, so some retriable error are not covered, enhance them in this pr

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

during run add-index, kill and restart tikv-worker multiple times, we can see logs like below

[2025/07/03 18:43:21.384 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155544154570753\": EOF"] ["job stage"=needRescan]
[2025/07/03 18:43:55.903 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": EOF"] ["job stage"=needRescan]
[2025/07/03 18:43:58.228 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": write tcp 127.0.0.1:51119->127.0.0.1:19000: use of closed network connection"] ["job stage"=needRescan]
[2025/07/03 18:44:00.355 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": write tcp 127.0.0.1:51143->127.0.0.1:19000: write: broken pipe"] ["job stage"=needRescan]
[2025/07/03 18:44:02.359 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": dial tcp [::1]:19000: connect: connection refused"] ["job stage"=needRescan]
[2025/07/03 18:44:04.562 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": write tcp 127.0.0.1:51182->127.0.0.1:19000: use of closed network connection"] ["job stage"=needRescan]
[2025/07/03 18:44:07.144 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": write tcp 127.0.0.1:51204->127.0.0.1:19000: write: broken pipe"] ["job stage"=needRescan]
[2025/07/03 18:44:09.148 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": dial tcp [::1]:19000: connect: connection refused"] ["job stage"=needRescan]
[2025/07/03 18:44:11.335 +08:00] [WARN] [job_worker.go:173] ["meet retryable error when writing to TiKV"] [keyspaceName=SYSTEM] [category=ddl-ingest] [error="Put \"http://localhost:19000/write_sst?cluster_id=7522790446772064389&commit_ts=459155553303396353\": write tcp 127.0.0.1:51229->127.0.0.1:19000: write: broken pipe"] ["job stage"=needRescan]

• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @D3Hunter. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 69.23077% with 12 lines in your changes missing coverage. Please review.

Project coverage is 73.1859%. Comparing base (91dcec4) to head (003b447).
Report is 5 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #62191        +/-   ##
================================================
+ Coverage   72.9181%   73.1859%   +0.2678%     
================================================
  Files          1740       1771        +31     
  Lines        483072     491205      +8133     
================================================
+ Hits         352247     359493      +7246     
- Misses       109244     109383       +139     
- Partials      21581      22329       +748     

Flag	Coverage Δ
integration	52.7186% <0.0000%> (?)
unit	72.1985% <69.2307%> (+0.0391%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.7804% <ø> (ø)
parser	∅ <ø> (∅)
br	46.3221% <ø> (-0.0128%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-07-03 10:48:50.670351889 +0000 UTC m=+1564783.393530873: ☑️ agreed by wjhuang2016.
• 2025-07-03 12:22:57.165747186 +0000 UTC m=+1570429.888926170: ☑️ agreed by tangenta.

[D3Hunter]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, tangenta, wjhuang2016

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/ingestor/OWNERS [D3Hunter,tangenta,wjhuang2016]
• pkg/lightning/OWNERS [D3Hunter]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment