-
Notifications
You must be signed in to change notification settings - Fork 6k
ddl,lightning: fix ingest data unexpectedly using zero commit ts #48797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi @tangenta. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with 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/test-infra repository. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #48797 +/- ##
================================================
+ Coverage 71.0864% 72.6656% +1.5791%
================================================
Files 1365 1391 +26
Lines 404572 411244 +6672
================================================
+ Hits 287596 298833 +11237
+ Misses 97010 93525 -3485
+ Partials 19966 18886 -1080
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Benjamin2037, 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:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest lgtm
/retest |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
What problem does this PR solve?
Issue Number: close #48804
Problem Summary:
When
ResetEngine
failed because of timestamp allocation error likePD:tso:ErrGenerateTimestamp
, the engine manager is not cleaned. In the next retry, engine manager invokesImportEngine
again, leavingbackend.TS
as the zero value.tidb/br/pkg/lightning/backend/local/local.go
Lines 1761 to 1763 in c467718
What is changed and how it works?
This PR sets both
engineInfo.openEngine
andengineInfo.closedEngine
tonil
if there is an error duringResetEngine
. In the next retry, engine manager will open a new backend and allocate TS.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.