First to answer the RAM question, Kapacitor doesn't store all data for the max window size rather each window stores what it needs and nothing more. So if a user adds a task with a 24hr window the rest of your tasks will remain the same, and Kapacitor will only need extra capacity for what ever the new task requires.
As for the question about multiple Kapacitor instances and the relay, see this question https://groups.google.com/forum/?pli=1#!searchin/influxdb/kapacitor$20relay$20subscriptions%7Csort:relevance/influxdb/yImf4Uok2T4/EPa0liC-AgAJ . In general subscriptions and the relay do not work well together, because of the duplicate data problem. On Tuesday, November 22, 2016 at 11:37:08 AM UTC-7, [email protected] wrote: > > nath! > > We may have a setup where one instance of influxdb is shared between > multiple teams but each team may get their own kapacitor. So in this model > if a new kapacitor instance needs to be created one would have to update > relay config to specify new kapacitor end point. > > I wanted it to be seamless for teams to spin new kapacitor instances > without any need to update relay configuration. > > Having said the above, i wanted the kapacitor to somehow point to primary > or secondary whichever is available (incase one is down). Using > loadbalancer dns name will end up subscribing kapacitor to both influxdbs > and wont work again. I can use cname to influxdb primary and if influxdb > primary is not available then i can point cname to secondary but there is > going to be alerting downtime with it. > > -- 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/8bd59c5b-86b5-47e0-9463-ceaf4f5214f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
