This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
restore: fix gc life time not recovered after table restore #218
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amyangfei
added
priority/normal
type/bug-fix
Bug fix
Should Cherry-pick
This PR should be cherry-picked back the previous release train
labels
Jul 23, 2019
amyangfei
added
the
status/PTAL
This PR is ready for review. Add this label back after committing new changes
label
Jul 23, 2019
kennytm
reviewed
Jul 23, 2019
/run-all-tests |
kennytm
reviewed
Jul 24, 2019
kennytm
reviewed
Jul 24, 2019
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
kennytm
reviewed
Jul 24, 2019
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
kennytm
added
status/LGT1
One reviewer already commented LGTM (LGTM1)
and removed
status/PTAL
This PR is ready for review. Add this label back after committing new changes
labels
Jul 24, 2019
/run-all-tests |
zier-one
approved these changes
Jul 25, 2019
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
kennytm
added
status/LGT2
Two reviewers already commented LGTM, ready for merge (LGTM2)
and removed
status/LGT1
One reviewer already commented LGTM (LGTM1)
labels
Jul 25, 2019
amyangfei
added a commit
to amyangfei/tidb-lightning
that referenced
this pull request
Jul 27, 2019
amyangfei
added a commit
that referenced
this pull request
Jul 29, 2019
kennytm
removed
the
Should Cherry-pick
This PR should be cherry-picked back the previous release train
label
Aug 26, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
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.
What problem does this PR solve?
feedback from DBA, sometimes after import data successfully with lightning,
tikv_gc_life_time
remains100h0m0s
and not recovers to the original value (often10m0s
).What is changed and how it works?
This is caused by concurrent execution of
restore table
, and thetikv_gc_life_time
update timeline maybe intersect like following:We query
tikv_gc_life_time
from downstream database before execution of restore table onceCheck List
Tests
Related changes