-
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
[1.2.0] panic: interface conversion: tsm1.Value is tsm1.IntegerValue, not tsm1.FloatValue #8085
Comments
@ranjithruban Does your version of telegraf include this change? influxdata/telegraf#2277 Can you show the output of |
Also, can you attach the output of |
@jwilder no , we are using telegraf 1.2.0 , this data was from consul telemetry plugin sending to statsd with some statsd templates added. Also i have another panic with same traces on another metric below. Had to drop the shard and move wal to recover influxdb from this error. Once it paniched influxdb was not able to recover properly with below error. Mar 2 11:32:55 localhost influxd[19008]: [I] 2017-03-02T10:32:55Z Failed to open shard: 173: [shard 173] field type conflict service=store I have the corrupted shard 173 saved if it helps in debugging. show shards name: test |
Can attach shard 173? |
Added tsm files. 47mb file. Please see if you can download this. |
@ranjithruban Got it. Thanks. |
@ranjithruban It looks like the problem is the |
@jwilder thanks. I have seen the "Field type conflict, dropping conflicted points: dropping" in telegraf in some of the measurements we use but not for consul/ or for the custom application measurement in second panic. Not really sure why it allowed write in some case. |
@ranjithruban I would also check your client to ensure that whatever is writing to I can attach the problem series keys if that would help. |
Yes i will check that. Please attach if it. To be clear can this bug be fixed in a way that that write are not allowed even if client send it ?. In our case multiple measurements are sending such values and some are java spring metrics. |
@ranjithruban There is a bug in the database in that it allowed two different field types for the same measurement. We'll need to fix that to prevent the panic and the shard failing to load. Regardless, writing data with different fields is not valid. You will end up with data being dropped or write errors when this is fixed as the database cannot support different field types for the same measurement. You'll need to use different field names, different measurements or ensure they all write the same field type. |
@jwilder Great, thank you. 👍 |
@ranjithruban Would you be able to test out #8092 to see if it prevents you shards from getting into an inconsistent state? We haven't been able to reproduce the issue yet. |
@jwilder Yes i will test it and update the results. |
Hello
Using influxdb 1.2.0 we are hitting the below panic occasionally.
Not able to see any duplicate report open for this. Please tell me if this is fixed in 1.2.1 or is it a new bug.
Regards
Ranjith
The text was updated successfully, but these errors were encountered: