[
https://issues.apache.org/jira/browse/FLINK-14981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-14981:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor features (was:
auto-deprioritized-major features stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> web frontend support dynamic adjustment of the log level
> ---------------------------------------------------------
>
> Key: FLINK-14981
> URL: https://issues.apache.org/jira/browse/FLINK-14981
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Affects Versions: 1.7.2, 1.8.2, 1.9.1
> Reporter: liu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> features
> Attachments: change llog level(Storm).png
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> In a production environment, sometimes the application behaves differently
> than expected, which requires the log debugging mode to be turned on to
> locate the problem. If the debug log is turned on when the program is
> started, the amount of data will be very large, causing the web frontend to
> crash. If it is not turned on, the program is a black box and cannot be
> debugged.
> Can flink support dynamic adjustment of the log level like Storm and set the
> expiration time at the same time. the original log level will be restored as
> soon as the time expires. This will not make the program run like a black
> box, nor print too many logs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
