This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
syncer/dbconn: add more retry error (#1903) #1916
Merged
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 #1903
What problem does this PR solve?
Auto retry for
and tidb'smysql.ErrInvalidConn
kv.RetryableErr
(by pingcap/tidb-tools#452).close #1825
What is changed and how it works?
When sql client interrupt (e.g. manually killed bykill tidb xxx
), go-mysql will returnmysql.ErrInvalidConn
and this error is safe to auto-retry build the connectionkv.RetryableErr
(currently only caused by TxnLockNotFound) is retryable too.Check List
Tests
Code changes
Side effects
Related changes