[
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 features stale-minor (was:
auto-deprioritized-major features)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, features, stale-minor
> 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)
