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

PITR: Flow history retention interval settings from the master #7125

Closed
bmatican opened this issue Feb 5, 2021 · 1 comment
Closed

PITR: Flow history retention interval settings from the master #7125

bmatican opened this issue Feb 5, 2021 · 1 comment
Assignees
Labels
area/docdb YugabyteDB core features

Comments

@bmatican
Copy link
Contributor

bmatican commented Feb 5, 2021

Since history retention dictates how many versions we keep in MVCC, we need to ensure that snapshots are taken at a regular interval, which should be smaller than the history retention window.

However, we definitely cannot ensure that users would respect that. Even if we end up doing this ourselves, internally, we might still end up with delays or the snapshotting might get jammed for various reasons (ie: bugs?).

An easy solution for this then would be to just make sure we have the master can force an increase of the history retention on the TS, if PITR data integrity could be affected.

@bmatican
Copy link
Contributor Author

Done as part of
f65f209
896e1e3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features
Projects
None yet
Development

No branches or pull requests

2 participants