[influxdb] Continuous queries for top 5 values

2017-01-09 Thread rtv2222
Hi, I would like to create continuous queries to precompute the top 5 values from a given table that holds say the mean cpu consumption of a set of devices. Here is the CQ CREATE CONTINUOUS QUERY top5cq ON metrics RESAMPLE EVERY 1h FOR 24h BEGIN SELECT top(mean_cpu, 5) as mean_cpu,

Re: [influxdb] kapacitor -- node|last() function

2017-01-09 Thread brendan . horan
Hi Ross, Thanks for the reply. I do see the error in the `kapacitor show`, I must of missed it the first time! Here is the message : "Error: last3: invalid influxql func last with field uptime: invalid field type: " I don't get why that is ? The influxdb query "select last(uptime) from

Re: [influxdb] ElasticSearch, Aerospike, InfluxDB with Kafka - which works best for time-series data?

2017-01-09 Thread Todd Persen
Just a little background on the CERN results, since I’m not sure it’s clear in their presentation - they were using a very old version of InfluxDB (either v0.8 or v0.9), and it had very different (read: underwhelming) performance characteristics back then. We’ve moved to an all-new storage engine

[influxdb] ElasticSearch, Aerospike, InfluxDB with Kafka - which works best for time-series data?

2017-01-09 Thread baden0x1
In working on a data ingestion platform, one of the requirements is a low-latency real-time ML-related response using Kafka Streams. Kafka is used as the message broker, and as of v0.10, Kafka Streams will be used in the place of something like Flink or Spark. Given the TICK stack, how would

Re: [influxdb] kapacitor -- node|last() function

2017-01-09 Thread Ross McDonald
​If the task stops executing, there should be an error stating why it was stopped next to the `Error:` heading in the `kapacitor show` output. Can you share the output to the output of `kapacitor show` for your task? Is there anything in the Kapacitor service logs for your task that look like an

[influxdb] Re: InfluxDB constantly restarting

2017-01-09 Thread Paul Seymour
Turns out the OOM killer was kicking in on these. I have increased the memory to 32gb on the servers but it's cycling around this shard for over 15 minutes now. This particular DB is 150gb in size. This shard is only 5.5gb in size 5.5G 889 On Monday, 9 January 2017 13:51:00 UTC, Paul

[influxdb] InfluxDB constantly restarting

2017-01-09 Thread Paul Seymour
Hello, Running v1.1.0 on CentOS 7 and following a config change (to disable query logging) and restart now getting this:- 13:40:50 write failed for shard 889: engine: cache-max-memory-size exceeded: (1074008687/1073741824) Amongst many others and then Influx restarts and goes through it all