You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2022/06/20 06:50:00 UTC
[jira] [Commented] (FLINK-28125) Promote leadership changing logs to INFO level
[ https://issues.apache.org/jira/browse/FLINK-28125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556220#comment-17556220 ]
Weijie Guo commented on FLINK-28125:
------------------------------------
Hi [~xtsong] , I am interested in this ticket, would you like to assign it to me?
> 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
> Priority: Minor
> Labels: 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.7#820007)