-
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
panic: unsupported value type during encode fields: int64 #2232
Comments
+1 |
It happens on rc23 too:
|
Sounds like it was not handled then. |
I also noticed the query results are slower (than rc17 I ran for a week), even with empty db |
Thanks for the reports. I'd like to know why you believe query performance has degraded. We did Philip On Saturday, April 11, 2015, Ehsan Azar notifications@github.com wrote:
|
@otoolep at this point it is just the perceived response time, from the time I issue a query to the time it returns back with results, it used to be instantaneous. |
#2261 should fix this. |
Should be fixed now. |
@otoolep is it going to be added to some rc24 perhaps? I am eager to test |
Yes, this change will be part of RC24. |
I'm still seeing this on 0.9.2.
|
@analytically What led to that panic? Can you show a sample of the data being written? Are you writing directly via the API or using the Go client or another library? |
I think I was writing null (nil?) values to the HTTP API. This caused Influx to crash. |
InfluxDB 0.9.0-RC22
This is in a LXC Container running Ubuntu Trusty; so I just grabbed RC22 like
wget "http://get.influxdb.org/influxdb_0.9.0-rc22_amd64.deb" dpkg -i influxdb_0.9.0-rc22_amd64.deb
Enabled graphite in the config and the monitoring at the bottom in
/etc/opt/influxdb/influxdb.conf
and started up influxdb; Diamond is outputting metricsThe text was updated successfully, but these errors were encountered: