[ https://issues.apache.org/jira/browse/FLINK-21747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300665#comment-17300665 ]
tim yu edited comment on FLINK-21747 at 3/13/21, 1:10 AM: ---------------------------------------------------------- Hi [~chesnay], Thanks for your suggestion, but that is not a perfect way. Should we shorten task name and operator name of some metrics ? Hi [~jark], Do you have any good suggestion? was (Author: yulei0824): Hi [~chesnay], Thanks for your suggestion, but that is not perfect way. Should we shorten task name and operator name of some metrics ? Hi [~jark], Do you have any good suggestion? > 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 stream job with insert statement whose size is too long, it report > metrics to influxdb. I find many influxdb exceptions that contains "max key > length exceeded ..." in the log file of job manager . The job could not write > the metrics to the influxdb, because "task_name" and "operator_name" is too > long. -- This message was sent by Atlassian Jira (v8.3.4#803005)