On Tuesday, December 13, 2016 at 3:49:39 PM UTC-5, Ross McDonald wrote: > I believe this is due to the default row limit in InfluxDB's HTTP handler, > not Kapacitor. Can you try setting InfluxDB's max-row-limit (in the HTTP > configuration) to 0? For example: > > ``` > > [http] > > max-row-limit = 0 > ``` > > > Thanks, > > Ross > > > > > > On Tue, Dec 13, 2016 at 11:57 AM, <[email protected]> wrote: > Hi all, > > > > When I run the following TICKscript: > > > > batch > > |query('SELECT mean(UPTIME) as meanUptime FROM > devices."three_weeks_rp".monitorData') > > .groupBy(*) > > .period(15m) > > .every(15m) > > .align() > > |influxDBOut() > > .database('devices') > > .retentionPolicy('test_rp') > > .measurement('meanMonitorData') > > .precision('s') > > > > It only inserts 10000 datapoints on devices.test_rp.meanMonitorData. I know I > have more than 100000 devices (deviceId is a tag) and data has been saved for > all of them every 5 minutes. > > > > When I run > > kapacitor show <my batch task> > > I get > > > > .... > > DOT: > > digraph batch_downsample_task { > > graph [throughput="0.00 batches/s"]; > > > > query1 [avg_exec_time_ns="0s" batches_queried="10000" points_queried="10000" > query_errors="0" ]; > > query1 -> influxdb_out2 [processed="10000"]; > > > > influxdb_out2 [avg_exec_time_ns="27.349µs" points_written="10000" > write_errors="0" ]; > > } > > ... > > > > Why batches_queries is 10000? Is there a configuration for this? > > That value increases by 10000, after 45 minutes(batch ran 3 times), value is > 30000 > > > > Best regards, > > > > Carlo > > > > > > -- > > 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/7d3b52c5-a48f-4110-82f6-8cabb0ff1c22%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout.
Hi Ross, Sorry for late reply. I changed the max-row-limit to 0 (even though documentation does not say that a zero value means no limit), but still I process 10000, see results after executing kapacitor show <task_name>: query1 [avg_exec_time_ns="0s" batches_queried="10000" points_queried="10000" query_errors="0" ]; query1 -> influxdb_out2 [processed="10000"]; influxdb_out2 [avg_exec_time_ns="103.297µs" points_written="10000" write_errors="0" ]; I even changed the max-row-limit to 200000 to see if something changes but it is still the same. Is there anything else I need to do? Also after changing max-row-limit to zero and executing a query (using the java client) that must return 200000 items it returns 10000. -- 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/c465726d-0317-4f1a-9f6b-5c6580a51883%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
