[
https://issues.apache.org/jira/browse/FLINK-33320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777522#comment-17777522
]
RocMarshal commented on FLINK-33320:
------------------------------------
Hi, [~fanrui] Thank you for the assign~ I'm willing to contribute to this
ticket.
Although this change is relatively minor, I still want to confirm if there is
any other discussion needed before starting the contribution. Such as
discussion or FLIP. Thank you very much~
> Support Dynamic Logger Level Adjustment
> ---------------------------------------
>
> Key: FLINK-33320
> URL: https://issues.apache.org/jira/browse/FLINK-33320
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: RocMarshal
> Assignee: RocMarshal
> Priority: Major
> Labels: REST_API, runtime
>
> During the process of routine program debugging or troubleshooting, analyzing
> system logs is a common approach.
> Comprehensive and detailed system logs contribute to improved visibility of
> internal system execution information and also enhance the efficiency of
> program debugging or issue troubleshooting.However, comprehensive and
> detailed log settings can lead to the following issues:
> # A sharp increase in log volume, accelerating disk occupancy.
> # Potential risks of system performance degradation due to a large volume of
> log printing.
> # The need to simplify log configuration subsequently.
> Therefore, introducing a mechanism to dynamically adjust the online log
> output level in the event of diagnosing online issues or debugging programs
> could be meaningful.
> This mechanism should ideally provide the following two basic capabilities:
> # Dynamically adjust log levels.
> # Query the current log levels of the JM/TM in the cluster.
>
> The proposal doc:
> https://docs.google.com/document/d/1s2XQzet_8oPhMs3WyDhP_pPhAE3d1Gdw_qR4W0nKtlY/edit?usp=sharing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
