-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
DROP SUBSCRIPTION query called on invalid retention policy corrupts database #5545
Comments
Cannot reproduce this in latest version (0.10.0). |
@robinsk can the issue be closed then? |
I guess. Though it would be interesting to know if there is a way to get the data out and use in a new db. It seems the data is intact, because the new upgrade util didn't fail, but the server fails starting when replaying a |
I've hit the same issue with
When trying to restart the database, it crashes again:
|
@robinsk It looks like you ran the exact same command that I did. I think this is caused by a
Which works without issue. I've also tested this on a cluster, and it ends up corrupting every node, which is not good. |
@rossmcdonald is there a way to get the data back ? |
It seems like I accidentally corrupted the database by running a
DROP subscription
query while playing around with kapacitor.We installed kapacitor and started it with this config.
Since we didn't specify any subscriptions, kapacitor set up the following:
I changed the kapacitor config to only have the subscription
telegraf = ["default"]
, and figured I should delete the old subscription on_internal
:That produced the following output:
So I found this documentation (https://github.com/influxdata/influxdb/blob/master/influxql/INFLUXQL.md) and added quotes to it:
Output:
I didn't care too much about the output, thinking I still had my drop syntax wrong, but when I ran
select * from _internal.monitor
I got this:It turns out influxdb died. Here's what the logs said: https://gist.github.com/robinsk/ad7564ddeb469fdb69e7#file-influxdb-log
Mainly:
When trying to start the influxdb service again, it fails, with almost the same things in the logs:
https://gist.github.com/robinsk/ad7564ddeb469fdb69e7#file-influxdb_starting-log
Is there any way to restore normal operations on this database, or do I have to restore from backup? This is in a vm in vagrant for testing, so it didn't matter that much this time, but that makes me reluctant of running the same in production.
The text was updated successfully, but these errors were encountered: