-
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.3] panic when query with 'select * from measurement' #4020
Comments
@airyland a simple panic log is not diagnostic enough. Some details that might help:
|
select count("user.uuid") from event => count 60490 So I may import some incorrect point with wrong event.value. But will 6w points cause influxdb to stop? |
I still cannot remember I wrote data with such a big value.. |
@airyland how are you writing the points? Direct HTTP calls, a library, Graphite plugin, etc.?
Assuming this is a single node system, that shouldn't lead to any panics.
I don't understand what you mean by "6w points". Six weeks of points is not a large amount of data and should cause no issues. If the query Can you paste in the results of |
|
I use Direct HTTP calls to insert points. |
Moving comment from #4018 (comment) to here:
|
@airyland can you paste in the log just before and including the panic when you run |
Sorry, I have to drop the database and reinsert points as other people needed the correct data. But this also happens in another measurement with different problem. I am sure I didn't import a point with such a big number. I checked my code and make sure that every "event.value" equals '1i'.
{"results":[{"series":[{"name":"event","columns":["time","distinct"],"values":[["1970-01-01T00:00:00Z",[9061497862447970,9063696952209719,9070099879571555,9065715607101795,9067012600325427,9068991824803638,9068089898787427,9070310413514293,9060393253285943,9115166971356722,9060204338492257,9061510075736628,9064805037270373,9119767733482084,9114270192449075,1,9070087830332723,9062399821964593,9062421363963191,9063708984882484,9062614556883298,9116270909022519,9117580759806566,9065698373742648,9119780638505314,9115368898507109,9115179953828915,9117384063738672,9070117881471536,9118461258248291,9070113619928372,9067896658473826,9061506455123769,9067003342042417,9118466325362994,9066991192531554,9116266463245923,9118482719389028,9063495024927797,9119556559201846,9060217961789541,9116266597344057,9117396878386276,9115189251564902,9063481385169510]]]}]}]} but {"results":[{}]} |
Please paste in a sample of your write statements for the |
Not sure if this is the same... I'm collecting data from collectd. Everytime I run the query below it crashes... This working last night for me but my cluster wasn't consistent. I cleared all the data about a few hours before... Notes
|
We've had a complete refactor of the query engine since this bug. Please try it again with the most recent version and reopen if this bug still exists. Thanks! |
The text was updated successfully, but these errors were encountered: