On Mon, Nov 28, 2016 at 1:20 PM, Sean Beckett <[email protected]> wrote:
> Why not have all three retention policies on the same InfluxDB instance? > We want to have multiple instances to improve performance. > There's no easy way to downsample from one InfluxDB instance to another, > so the three instance setup sounds unnecessarily complicated > We have written software that can broadcast data to multiple influx instances simultaneously as well as roll up the data differently for each one so this multiple influx instance approach is simple for us. > > Your users or your proxy would still have to route the query to the right > retention policy, but you have that basic issue either way. A proxy seems > reasonable until https://github.com/influxdata/influxdb/issues/7198 is > ready. > ok thx. > > On Mon, Nov 28, 2016 at 1:57 PM, <[email protected]> wrote: > >> We want to have three influx db instances: >> >> 1. 1 day retention policy: 15s rollups >> 2. 1 month retention policy: 10m rollups >> 3. 5 year retention policy: 12h rollups >> >> >> We want to hide that we have three servers from our users and instead >> allow our users to issue queries to a single influx db server and have that >> server route the queries to the above three influx db instances. >> >> My plan is to write my own proxy server that does the following: >> >> 1. Accepts incoming queries >> 2. Computes the time range for the query >> 3. Depending on the time range, forwards the query to some or all of the >> 3 back ends. >> 4. Retrieves the responses and merges them together into a single response >> 5. Send the response back to the client >> >> >> By doing this, it looks like there is just one influx server even though >> there are three. >> >> Question: >> >> Is writing my own proxy server the best way to go? Or does influx provide >> an easier way to do this? >> >> >> Thanks in advance >> >> -- >> 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/ms >> gid/influxdb/a5fd0cbf-fc28-4679-89e6-54b000670234%40googlegroups.com. >> 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 a topic in the > Google Groups "InfluxData" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/influxdb/pY2YTtvVXwY/unsubscribe. > To unsubscribe from this group and all its topics, 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/CALGqCvMoboEaj__Q7NghpurADYmyjcYOKsFGbfa85jdu9 > wmsWw%40mail.gmail.com > <https://groups.google.com/d/msgid/influxdb/CALGqCvMoboEaj__Q7NghpurADYmyjcYOKsFGbfa85jdu9wmsWw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAAfiYQcDyaMLku9Rh-WANPxcboS8ZSH_Q-ayDEAeGiZ4WhQF3A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
