You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/08/21 15:09:00 UTC
[jira] [Updated] (FLINK-32710) The LeaderElection component IDs for running is only the JobID which might be confusing in the log output
[ https://issues.apache.org/jira/browse/FLINK-32710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-32710:
-----------------------------------
Labels: pull-request-available starter (was: starter)
> The LeaderElection component IDs for running is only the JobID which might be confusing in the log output
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-32710
> URL: https://issues.apache.org/jira/browse/FLINK-32710
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.18.0
> Reporter: Matthias Pohl
> Assignee: Jiadong Lu
> Priority: Minor
> Labels: pull-request-available, starter
>
> I noticed that the leader log messages for the jobs use the plain job ID as the component ID. That might be confusing when reading the logs since it's a UUID with no additional context.
> We might want to add a prefix (e.g. {{job-}} to these component IDs.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)