[
https://issues.apache.org/jira/browse/IGNITE-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330666#comment-16330666
]
Stanislav Lukyanov commented on IGNITE-6946:
--------------------------------------------
After some research, it seems that we can update logger configurations for JUL,
log4j, log4j2 (+ SLF4J backed by these loggers) on the fly out of the box.
JUL allows to do that via an MXBean.
Log4j and log4j2 can be configured to watch changes of the log4j.xml or
log4j2.xml file, picking up new configuration if it has changed.
For Log4j we need a small code update in Ignite to enable this.
For Log4j2 no updates are required per se, but it would be nice to enable
config changes watches in the default config file (ignite-log4j2.xml).
> Change Ignite Logger configuration on the fly
> ---------------------------------------------
>
> Key: IGNITE-6946
> URL: https://issues.apache.org/jira/browse/IGNITE-6946
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.3
> Reporter: Alexey Popov
> Assignee: Stanislav Lukyanov
> Priority: Major
>
> It would be great if we can change Ignite Logger configuration on the fly
> without restarting the cluster node. It will really help to debug an issue
> while it is reproducible at the current cluster state.
> It should be done within the configured type of a logger, i.e. it is enough
> to change logging levels without changing the Logger type itself.
> Such configuration change should be done for all supported logger types (JUL,
> log4j, log4i2 and others).
> Also it should be done easily, for instance, via Visor, WebConsole or any
> other user-friendly tool ).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
