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

figure out metrics expiry #2

Open
dgryski opened this issue Nov 20, 2016 · 2 comments
Open

figure out metrics expiry #2

dgryski opened this issue Nov 20, 2016 · 2 comments

Comments

@dgryski
Copy link
Collaborator

dgryski commented Nov 20, 2016

No description provided.

@kanatohodets
Copy link
Owner

The general plan is to change the write buffer to store a time.Time in the text metric set (perhaps along with the hashed metric value), then filter out old metrics from the write buffer data structures before giving them to indexes to materialize.

This plan was consciously broken for the text index when the active/standby bloom index bit was implemented. If we stick with bloom indexes, they'll just need to be regenerated from scratch every so often.

On Nov 20, 2016, at 10:12, Damian Gryski [email protected] wrote:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@dgryski
Copy link
Collaborator Author

dgryski commented Nov 20, 2016

For the bloom index (and optionally the new one I'm working on too), we can partition by time and expire old indexes after a certain period. For example, create one new index every minute, keep 10 in memory, and expire the oldest.

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

No branches or pull requests

2 participants