-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.9.4 & 0.9.5-nightly-6682752] Continuous Queries stop running #4646
Comments
Note: stopping and restarting the influxdb service starts the continuous queries running again. |
@dgnorton Any ideas? |
I may be experience a similar issue on InfluxDB version 0.9.4.1. Continuous queries just stop running after a while. I have four continuous queries that rollup data into various retention policies. One query has |
@njurgens that definitely seems wrong. If you restart the process do the CQs resume running? |
@njurgens do ad hoc queries execute and return? Basically, is the system otherwise healthy and CQs have just stopped running periodically? |
@beckettsean I'm able to still execute queries as normal. Data is still being written to the measurement's default retention policy and I can query that no problem. If I query any of the retention policies that are populated by my CQs, I only have data from before about 2015-11-06T06:40:00Z (around the time CQs stopped appearing in the logs). I'll restart the database and see if they resume running. Update: After I restarted InfluxDB and the CQs seem to be running again. |
Continuous queries started to hang again and queries to one of my retention policies timeout. This retention policy is the same as the one queried by the last CQ that ran (according to the logs). After restarting the database, CQs run again, but that retention policy remains unqueryable. |
Can you be more specific? Queries return bad values? Null values? Queries don't return? The process throws stack? |
@beckettsean Queries to that retention policy don't return. (Queries to other retention policies do return, though.) Other log items (potentially) of note:
I had started wondering if it's related to #3469 due to the cascading continuous queries, but that seems to be about write timeouts. Also possibly related: #4203, #3158 (though we are using |
I haven't seen this issue since upgrading to InfluxDB 0.9.5 a week ago. |
@brettdh are you still seeing this issue? If so, have you tried 0.9.5? |
I am still on 0.9.4.1, and I haven't been testing this actively, but I haven't noticed a hang since the last time I commented here. This issue is frustratingly intermittent, though, so I'm not confident it's gone until it can be reliably reproduced. @njurgens has been steadily storing new measurements in his 0.9.5 deployment, though, so that gives me some hope. :-) |
This is an old issue for a now unsupported version of InfluxDB. I'm going to close this, but please comment or make a new issue if you see this with 0.13 or newer. Thank you. |
Using the build, I create two continuous queries. One query runs every 5m and one query runs every 1h. The log shows the queries are successfully created and the queries begin to run.
After about and hour (sometime more, sometimes less) the queries stop running. The log shows no errors, just no continuous query activity. Using the admin console to list the continuous queries ("show continuous queries") returns no results. However, trying to recreate the query in the admin console reports an error, indicating the query already exists.
Below are snippets from the log file showing successful query creation and the queries executing for a period of time.
This has happened multiple times. Each time, I started fresh with a new database.
The text was updated successfully, but these errors were encountered: