Those are now called Retention Policies and they are part of the OSS database. Not sure if they fit your needs for multi-tenancy. Currently there is no easy way to have different databases physically stored on different mount points. All data is under a single umbrella directory, but the subdirectories are deterministic as they use the database and retention policy name. E.g., with "default" and "forever" retention policies in the "telegraf" database, this is the structure on disk:
root@sean-stable:/var/lib/influxdb/data/telegraf# ls default forever https://docs.influxdata.com/influxdb/v1.0/concepts/key_concepts/ https://docs.influxdata.com/influxdb/v1.0/concepts/glossary/#retention-policy-rp https://docs.influxdata.com/influxdb/v1.0/query_language/database_management/#retention-policy-management On Wed, Nov 2, 2016 at 8:17 AM, 'Dietmar Wolz' via InfluxData < [email protected]> wrote: > 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/i >> nfluxdb/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 [email protected]. > To post to this group, send email to [email protected]. > 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 > <https://groups.google.com/d/msgid/influxdb/43f8a014-99b5-461c-b9b9-5f17a04f5e66%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CALGqCvNJfJpX5bu_zjLq9LGsd9Geeo0uKQJcbmq-h%2BLo%2BjXhFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
