MySQL Plugin: inconsistent measurements

[bluebob]

Relevant telegraf.conf:

[[inputs.mysql]]
  servers = ["randompasswordremoved@tcp(127.0.0.1:3306)/"]
  metric_version = 2
  perf_events_statements_digest_text_limit  = 120
  perf_events_statements_limit              = 250
  perf_events_statements_time_limit         = 86400
  table_schema_databases                    = []
  gather_table_schema                       = false
  gather_process_list                       = false
  gather_user_statistics                    = false
  gather_info_schema_auto_inc               = false
  gather_innodb_metrics                     = false
  gather_slave_status                       = false
  gather_binary_logs                        = false
  gather_table_io_waits                     = false
  gather_table_lock_waits                   = false
  gather_index_io_waits                     = false
  gather_event_waits                        = false
  gather_file_events_stats                  = false
  gather_perf_events_statements             = false
  interval_slow                   = "30m"
  fielddrop = ["caching_sha2_password_rsa_public_key","rsa_public_key"]

System info:

Telegraf 1.10.2 running on RHEL7.5 64 bit

Steps to reproduce:

Telegraf was configured as per documentation with mysql block as given above, but outputting to a Kafka topic. A separate Telegraf (1.10.0) instance then consumes this topic and writes to an InfluxDB database that has had all mysql* measurements removed.

Expected behavior:

No errors seen

Actual behavior:

The Telegraf that is ingesting the data into Influx reports the following repeatedly:

2019-04-11T13:30:06Z E! [outputs.influxdb]: when writing to [http://hostnameremoved:8086]: received error partial write: field type conflict: input field "innodb_data_pending_fsyncs" on measurement "mysql" is type float, already exists as type integer dropped=1; discarding points

Given that innodb_metrics appears to be switched off in the configuration I'm a bit confused as to why this field is being created, and doubly so that it's being written with different value types.

Additional info:

MySQL instance being polled is community version 8.0.13 running on RHEL7-64bit

[danielnelson]

related #5529

[bluebob]

Changing the fielddrop line to:

fielddrop = ["caching_sha2_password_rsa_public_key", "rsa_public_key", "innodb_data_pending_fsyncs", "innodb_row_lock_current_waits"]

seems to stop all error messages from the InfluxDB ingest Telegraf.

[bglinkerman]

I have run into similar issues with this plugin:

Failed to write data - err = {"error":"write failed: partial write: field type conflict: input field \"innodb_buffer_pool_pages_misc\" on measurement \"ops_web_tools_mysql\" is type float, already exists as type integer dropped=1"}

[fxedel]

Hey @bluebob, has your issue been resolved with #9403?

[sjwang90]

@bluebob please re-open if isn't resolved with #9403. thanks @fxedel for the PR!