-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add support for arbitrary number of shard spaces with set retention policies #571
Comments
this looks really nice :) |
Hi, I just got back from vacations, is there any update on this ? |
I'm working on this and a few other things this week. Hope to have it done On Mon, Jun 16, 2014 at 6:45 AM, Julien Ammous notifications@github.com
|
Fixes #571. Removed the old long term and short term shards. Now if the user doesn't manually create a shard space, a catchall called "default" will be created the first time they write data in. Added API endpoints to list, create, and delete shard spaces. Made a breaking change to the old get shards API by changing the format since shortTerm and longTerm shards aren't guaranteed to be present. Shard spaces can be mapped to either a single database or any number of databases. Retention policies are enforced per server by a background routine that periodically checks shards in spaces that have retention policies to see if they have passed their expiration.
Fixes #571. Removed the old long term and short term shards. Now if the user doesn't manually create a shard space, a catchall called "default" will be created the first time they write data in. Added API endpoints to list, create, and delete shard spaces. Made a breaking change to the old get shards API by changing the format since shortTerm and longTerm shards aren't guaranteed to be present. Shard spaces can be mapped to either a single database or any number of databases. Retention policies are enforced per server by a background routine that periodically checks shards in spaces that have retention policies to see if they have passed their expiration. Conflicts: src/cluster/cluster_configuration.go
Currently we have short term and long term shards and data is assigned by what the first character is. We should change this so that assignment is set by database and a regex. Each shard space should have a data retention policy set as a duration. The database should automatically drop shards that are past the retention policy in any given shard space.
See this thread for more info: https://groups.google.com/forum/#!topic/influxdb/4aC0AMPCcFs
The text was updated successfully, but these errors were encountered: