-
Notifications
You must be signed in to change notification settings - Fork 495
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
add tikvGCLifeTime option #835
Changes from 1 commit
78cd587
7b73a31
553031d
bf55134
fc21aa7
35436f2
4019b27
5ef048b
4f43946
e687821
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -56,6 +56,9 @@ backupOptions: "--verbose=3" | |
initialCommitTs: "" | ||
# restoreOptions is the options of loader https://www.pingcap.com/docs-cn/tools/loader/ | ||
restoreOptions: "-t 16" | ||
# The time limit during which data is retained for each GC when backup, in the format of Go Duration. | ||
# When a GC happens, the current time minus this value is the safe point. | ||
tikvGCLifeTime: 3h | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it would better to use a long gc life time that impossible to reach as the default, e.g. 720h, which effectively "disable" the GC when backup in progress. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I think this should not even be an option: the controller should automatically hold open the GC. Here we can have a timeout option to timeout the backup if it does not complete and document that it helps limit performance degradation during backup due to maintaining the GC. TiDB is supposed to get a backup lock feature eventually.
weekface marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# By default, the backup/restore uses PV to store/load backup data | ||
# You can choose to store/load backup data to/from gcp, ceph or s3 bucket by enabling the following corresponding section: | ||
|
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.
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.
When adding new variable to chart, always remember to set a default in case of users not providing the variable.
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.
done