Skip to content
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

wrong data in database #7391

Closed
gescheit opened this issue Oct 1, 2016 · 2 comments
Closed

wrong data in database #7391

gescheit opened this issue Oct 1, 2016 · 2 comments
Assignees
Milestone

Comments

@gescheit
Copy link

gescheit commented Oct 1, 2016

In some cases values in base and values that was written are different.
System: influxdb 1.0.0-1, Ubuntu 14.04.3 LTS.

Steps to reproduce:

Use this script
Script constantly writes the same data to influx. The pattern of data is odd, but it causing the problem.

Expected data from gist example.
network,host=host rx=7094i 1474460700
network,host=host rx=4472i 1474460760
network,host=host rx=1850i 1474460820

Actual output of the script:
....
lines count 1849. duration 68
lines count 1853. duration 68
lines count 1857. duration 68
stopping. found bad value -9716
'name': 'network',
'values': [['2016-09-21T12:25:00Z', 'host', 7094],
['2016-09-21T12:26:00Z', 'host', -9716],
['2016-09-21T12:27:00Z', 'host', 12337]]}]}]}

@jwilder jwilder self-assigned this Oct 1, 2016
@jwilder
Copy link
Contributor

jwilder commented Oct 1, 2016

Thanks for the script @gescheit! I was able to reproduce this as well.

@jwilder jwilder added this to the 1.0.2 milestone Oct 1, 2016
jwilder added a commit that referenced this issue Oct 3, 2016
Integer blocks that were run length encoded could produce the wrong
value when read back out because the deltas were not zig zag decoded
before scaling the final value.  If the deltas were negative, as would
be seen in a counter that decrements by a constant value, the results
would be random with som negative and positive values.

Fixes #7391
jwilder added a commit that referenced this issue Oct 3, 2016
Integer blocks that were run length encoded could produce the wrong
value when read back out because the deltas were not zig zag decoded
before scaling the final value.  If the deltas were negative, as would
be seen in a counter that decrements by a constant value, the results
would be random with som negative and positive values.

Fixes #7391
@gescheit
Copy link
Author

gescheit commented Oct 4, 2016

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants