[
https://issues.apache.org/jira/browse/FLINK-16478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359207#comment-17359207
]
Yang Wang commented on FLINK-16478:
-----------------------------------
Just a side input, if you are running Flink on Kubernetes, then you could
simply edit the log4j properties ConfigMap, the log level could take effect
automatically.
For the Yarn deployment, it is a little difficult to do this manually. Because
you need to login the node, find the working directory of container and then
update the log4j.properties file.
> add restApi to modify loglevel
> -------------------------------
>
> Key: FLINK-16478
> URL: https://issues.apache.org/jira/browse/FLINK-16478
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: xiaodao
> Priority: Minor
> Labels: auto-deprioritized-major
>
> sometimes we may need to change loglevel to get more information to resolved
> bug, now we need to stop it and modify conf/log4j.properties and resubmit it
> ,i think it's better to add rest api to modify loglevel.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
