-
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
Table creation / deletion oddities when writing from Telegraf | Requires Investigation #25695
Comments
I think Telegraf is excess noise here. We should be able to reproduce using just curl against the v1 or v2 write APIs. |
Provided config file for telegraf. |
Telegraf 1.30 appears to work but 1.33 might be an issue, |
Mac M2 Telgraf sending data to OSS 3 running in ESXi Linux Ubuntu 20.4 |
An odd scenario where deleting a DB seems to work, but then when recreating it, tag issues are created. This is primarily seen on Telegraf writing on 1.33, and doesn't appear when writing line protocol from the CLI (on macOS). So needs investigation in several areas.
Steps to reproduce:
The cpu DB has been created
The cpu DB has been deleted
Say's it's writing, but doesn't, and doesn't create DB or table
Fails on write, error says we're trying to add a tag that doesn't exist | Telegraf in v2 continues to say it's writing, but doesn't
The cpu DB has returned, with no data tables, but contains system tables
Expected behaviour:
When Telegraf says it's writing, it should create a new DB, a new table, write the data, and have no tag issues, since it's a fresh new database and table.
Actual behaviour:
InfluxDB is saying that there is an attempt to write a new tag, as if there is an old table it's trying to write to and can't, and therefore it doesn't write to a new table at all (but it does create the DB).
Seems like the system:
It should never discover a table. Perhaps due to soft delete?
Environment info:
System: Linux ARM
Storage: Memory
Telegraf: v1.33
Logs:
error_message: "Detected a new tag 'label' in write. The tag set is immutable on first write to the table."
The text was updated successfully, but these errors were encountered: