Since we currently evaluate InfluxDB for our product we would like to know the current status of the N shard spaces idea to separate the physical storage space of different tenants. Is it done? If yes, is it part of the open source offer or of the commercial enterprise solution? If no, what is your current approach regarding multi tenancy? What is offered by the open source solution, what by the enterprise solution? Is something more on your roadmap?
On Tuesday, May 13, 2014 at 3:48:19 PM UTC+2, Paul Dix wrote: > > We're currently thinking about implementing something called shard spaces. > If you look at the config file ( > https://github.com/influxdb/influxdb/blob/master/config.sample.toml#L120-L159) > > there are currently two shard spaces: short term and long term. We're going > to split this out so you can have N shard spaces and give each of them a > name. The idea being that a shard space can be associated with a database > first, then if you want to match against series names or regexes. So you > could have different shard spaces per database and each shard space will > have its own retention policy. I think that will do what you need? > > -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+unsubscr...@googlegroups.com. To post to this group, send email to influxdb@googlegroups.com. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/43f8a014-99b5-461c-b9b9-5f17a04f5e66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
