[
https://issues.apache.org/jira/browse/FLINK-16478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058707#comment-17058707
]
Yang Wang commented on FLINK-16478:
-----------------------------------
[~chesnay] Thanks for you response. I think it is not enough.
For k8s deployment, we could update the configmap and the changed
log4j.properties will automatically be mount into the JM/TM. So it is enough in
such case.
However for Yarn deployment, it is not very easy to find the location of
log4j.properties. Also we need to login to the Yarn cluster and have enough
permission to change the file. It is usually impossible, especially in the
production environment.
If we could support update the log level by rest/webui, it will be very
convenient.
> 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
>
> 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)
