ddl: eliminate ingest step for add index with local engine (#47982) #48099
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #47982
What problem does this PR solve?
Issue Number: close #47981
Problem Summary:
Previously, when
tidb_enable_dist_task
is enabled, the ingest step(step 3) is separated from read-index step(step 1). This cause the problem that if a TiDB crashes in ingest step, index data in local disk is lost. Because the disttask framework does not support changing step backward(like changing step 3 to step 1), it doesn't re-scan the lost index data. Finally, data inconsistency occurs.What is changed and how it works?
Merge the ingest step to read-index step by
Flush
every time a subtask is finished.Thus, the subtask will not be marked as
succeed
if ingest failed.replaceDeadNodesIfAny
will re-distribute these running subtask to another TiDB instance when the lease is expired.Check List
Tests
Before
After:
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.