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

Clearing sliceCache should also throw away timeStep #38

Open
iain-buclaw-sociomantic opened this issue Feb 1, 2016 · 0 comments
Open

Comments

@iain-buclaw-sociomantic
Copy link
Contributor

A common maintenance task would be to start writing out a new stat, only to find that we want more coarse or finer precision for it later down the line.

Carbon can reload it's storage schemas no problem, and we have plugins that can rewrite metadata files to sync with Carbon config, merging any "orphaned" slices in the process. However CeresNode keeps the timeStep in memory and will continue to create slices at a retention that no longer matches what Carbon or the CeresMetadata on disk says about the node.

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

2 participants