Skip to content
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

Proposal: define --gcttl of BR as the TTL after backup finished #308

Open
pingyu opened this issue Nov 10, 2022 · 2 comments
Open

Proposal: define --gcttl of BR as the TTL after backup finished #308

pingyu opened this issue Nov 10, 2022 · 2 comments

Comments

@pingyu
Copy link
Collaborator

pingyu commented Nov 10, 2022

Feature Request

Is your feature request related to a problem? Please describe:

The --gcttl is the TTL from the beginning of backup now, and users have to estimate the duration of backup + duration of other preparation before start a changefeed. However, it would be difficult to estimate the duration of backup. Once the duration is underestimated, the initial backup is wasted and must be performed again.

Describe the feature you'd like:

Define --gcttl as the TTL after backup finished. Then users only need to estimate their preparation time before start the changefeed.

Besides, --gctll defaults to 0, which means that user doesn't need a CDC, and holding GC safepoint is not necessary, for saving disk space.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@pingyu
Copy link
Collaborator Author

pingyu commented Nov 10, 2022

@haojinming @zeminzhou PTAL~

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant