Trying to insert a number larger than the largest signed 64-bit number kills influxd #3127
Assignees
Labels
Comments
|
jwilder
added a commit
that referenced
this issue
Jun 25, 2015
Field values that were out of range for the type would panic the database when being inserted because the parser would allow them as valid points. This change prevents those invalid values from being parsed and instead returns an error. An alternative fix considered was to handle the error and clamp the value to the min/max value for the type. This would treat numeric range errors slightly differently than other type erros which might lead to confusion. The simplest fix with the current parser would be to just convert each field to the type at parse time. Unfortunately, this adds extra memory allocations and lowers throughput significantly. Since out of range values are less common than in-range values, some heuristics are used to determine when the more expensive type parsing and range checking is performed. Essentially, we only do the slow path when we cannot determine that the value is in an acceptable type range. Fixes #3127
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On OSX with influx version 0.9 built from source
Running the command
kills influxd
The text was updated successfully, but these errors were encountered: