-
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.1] Derivative operation on strings panics db, sometimes causes data loss #3401
Comments
@j-rock - can you explain why you believe your data were corrupted? A query does not make any changes to data. |
Sorry for the delay. When I went back into the InfluxDB CLI...
|
@j-rock did you execute a If so, we should simplify this to "derivative on string should't panic" |
Let me replicate the failure scenario and give you better info. Hold on a few, please. |
https://gist.github.com/j-rock/562ee778ca2d10013ec8 Create a database called influxdb_database_1. Insert a series called "string" with values of type string (though they look like floating point numbers). Run a derivative operation on them. InfluxDB crashes with a panic. I check to see that the /data dir is still there (it is). Reboot InfluxDB. "show databases" comes up with nothing. I still "use" influxdb_database_1. "show series" comes up with the "string" series from before. "select * from string" comes up with database not found "influxdb_database_1". |
Thanks for the repro gist @j-rock. That is strange indeed. |
I'm able to repro the panic when taking the derivative of a string, which certainly needs to be fixed, but I don't get any data corruption when that happens.
|
What about "show databases/use mydb1"? |
Works fine
|
As an aside, |
I'm guessing if the panic is cut out that the data corruption won't happen in this case. In the mean time here is my config file. I've replaced the field 'bind-address' with filler. https://gist.github.com/j-rock/dedbefc2998cccabe139. |
I made the mistake of trying to perform a derivative operation on a column of strings.
InfluxDB 0.9.1 reported a panic:
In this case, 522.00000 was a string.
The next thing I knew, my InfluxDB instance crashed and upon restart, my data were corrupted. :/.
I avoid this by operating on floats (not strings!), but it seems like this error case could be handled better.
The text was updated successfully, but these errors were encountered: