Skip to content
This repository has been archived by the owner on Feb 16, 2022. It is now read-only.

Log prefix truncation #3

Open
superfell opened this issue Apr 5, 2019 · 0 comments
Open

Log prefix truncation #3

superfell opened this issue Apr 5, 2019 · 0 comments

Comments

@superfell
Copy link
Contributor

When using the logspec client, the cluster needs to regularly calculate a safe truncation point, and tell the log store to truncate the prefix of the log to that index.

The API server can consult with all the views to determine the smallest safe point across the cluster. Either the API tier can then issue the delete, or for more complex deployments where a single log is used across multiple DCs, and each DC has its own beam cluster, you'd probably want this truncation to be managed by a separate control plane.

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

No branches or pull requests

1 participant