Can you share the results of "SHOW CONTINUOUS QUERIES ON <database>" for each database on the system?
Is it possible for you to upgrade to 0.13 or to 1.0RC1? On Wed, Aug 24, 2016 at 8:10 PM, Meng <[email protected]> wrote: > We use a 192GB RAM, 24Core machine, here is the usage > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ > COMMAND > > 18170 user 20 0 90.937g 0.070t 6.050g S 115.3 28.3 3051:05 nfluxdb > > > > > and we still suffering CQ delay > > [continuous_querier] 2016/08/25 10:03:26 executing continuous query test > (2016-08-23 05:59:00 +0800 CST to 2016-08-23 06:00:00 +0800 CST) > [continuous_querier] 2016/08/25 10:05:23 executing continuous query test > (2016-08-23 05:58:00 +0800 CST to 2016-08-23 05:59:00 +0800 CST) > [continuous_querier] 2016/08/25 10:07:20 executing continuous query test > (2016-08-23 05:57:00 +0800 CST to 2016-08-23 05:58:00 +0800 CST) > [continuous_querier] 2016/08/25 10:09:09 executing continuous query test > (2016-08-23 05:56:00 +0800 CST to 2016-08-23 05:57:00 +0800 CST) > > > > > On Thursday, August 25, 2016 at 7:29:47 AM UTC+8, Sean Beckett wrote: >> >> The system appears to be unable to keep up with the CQ demand. What are >> the CPU and RAM usage on the server? >> >> On Wed, Aug 24, 2016 at 9:45 AM, Meng <[email protected]> wrote: >> >>> Hi, we are using influxDB v0.12.2, but we have a problem with continuous >>> query. >>> We define several CQs, after several hours we got logs like this >>> >>> >>> >>> [continuous_querier] 2016/08/19 19:19:10 executing continuous query >>> test (2016-08-19 18:59:00 +0800 CST to 2016-08-19 19:00:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/19 19:19:30 executing continuous query >>> test (2016-08-19 18:58:00 +0800 CST to 2016-08-19 18:59:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/19 19:19:50 executing continuous query >>> test (2016-08-19 18:57:00 +0800 CST to 2016-08-19 18:58:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/19 19:20:09 executing continuous query >>> test (2016-08-19 18:56:00 +0800 CST to 2016-08-19 18:57:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/19 19:20:30 executing continuous query >>> test (2016-08-19 18:55:00 +0800 CST to 2016-08-19 18:56:00 +0800 CST) >>> >>> ...... >>> >>> [continuous_querier] 2016/08/24 16:16:42 executing continuous query >>> test (2016-08-23 14:20:00 +0800 CST to 2016-08-23 14:21:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/24 16:18:46 executing continuous query >>> test (2016-08-23 14:19:00 +0800 CST to 2016-08-23 14:20:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/24 16:20:47 executing continuous query >>> test (2016-08-23 14:18:00 +0800 CST to 2016-08-23 14:19:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/24 16:22:52 executing continuous query >>> test (2016-08-23 14:17:00 +0800 CST to 2016-08-23 14:18:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/24 16:24:48 executing continuous query >>> test (2016-08-23 14:16:00 +0800 CST to 2016-08-23 14:17:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/24 16:26:52 executing continuous query >>> test (2016-08-23 14:15:00 +0800 CST to 2016-08-23 14:16:00 +0800 CST) >>> >>> [continuous_querier] 2016/08/24 16:28:53 executing continuous query >>> test (2016-08-23 14:14:00 +0800 CST to 2016-08-23 14:15:00 +0800 CST) >>> >>> >>> >>> at 2016/08/24 16:28:53, executing continuous query test (2016-08-23 14: >>> 14:00 +0800 CST to 2016-08-23 14:15:00 +0800 CST). >>> >>> The CQ named test suffers severe delay，is there any clue to explain why >>> this happened? >>> >>> -- >>> Remember to include the InfluxDB version number with all issue reports >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "InfluxDB" 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/97ef9bab-d1d6-471a-9fde-0d09e82b0dff%40googlegroups.com >>> <https://groups.google.com/d/msgid/influxdb/97ef9bab-d1d6-471a-9fde-0d09e82b0dff%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 InfluxDB version number with all issue reports > --- > You received this message because you are subscribed to the Google Groups > "InfluxDB" 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/57a65160-fcfd-4821-8ea8-84f65f8499d7%40googlegroups.com > <https://groups.google.com/d/msgid/influxdb/57a65160-fcfd-4821-8ea8-84f65f8499d7%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 InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" 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/CALGqCvPAo5E%2BnUOJtPjxF0iboyuRqLgdLj-QcoCh2OX0ziyw2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
