[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
