You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/05 10:40:01 UTC
[jira] [Updated] (FLINK-21747) Encounter an exception that contains
"max key length exceeded ..." when reporting metrics to influxdb
[ https://issues.apache.org/jira/browse/FLINK-21747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-21747:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was: auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> Encounter an exception that contains "max key length exceeded ..." when reporting metrics to influxdb
> ------------------------------------------------------------------------------------------------------
>
> Key: FLINK-21747
> URL: https://issues.apache.org/jira/browse/FLINK-21747
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics
> Affects Versions: 1.10.0
> Reporter: tim yu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> I run a streaming job with insert statement whose size is too large, it reports metrics to influxdb. I find many influxdb exceptions that contains "max key length exceeded ..." in the log file of the job manager . The job could not write any metrics to the influxdb, because "task_name" is too long.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)