[
https://issues.apache.org/jira/browse/FLINK-28125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28125:
-----------------------------------
Labels: pull-request-available stale-assigned starter (was:
pull-request-available starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Promote leadership changing logs to INFO level
> ----------------------------------------------
>
> Key: FLINK-28125
> URL: https://issues.apache.org/jira/browse/FLINK-28125
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Assignee: Weijie Guo
> Priority: Minor
> Labels: pull-request-available, stale-assigned, starter
>
> Currently, {{DefaultLeaderElectionService}} logs leadership changing events
> in DEBUG level, expecting the contender to log the changes in INFO level.
> This is fragile because there're many different {{LeaderContender}}
> implementations and not all of them print the logs properly. E.g.,
> {{JobMasterServiceLeadershipRunner}} logs the leadership changes in TRACE
> level.
> I'd suggest to revisit the logging of leadership changing, printing the INFO
> logs from {{LeaderElectionService}}. That probably also means removing the
> contender side logs to avoid redundancy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
