[
https://issues.apache.org/jira/browse/FLINK-21747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304643#comment-17304643
]
tim yu commented on FLINK-21747:
--------------------------------
Hello [~jark] and [~chesnay]
Through a review of metrics system code, I find that only the operator name is
truncated if it exceeds 80 characters length.
I encounter this issue, because this simple rule is not applied to job and task
name.
Should we truncate it if the name of job or task is too long ?
> 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: Major
>
> 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)
