You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Popov (JIRA)" <ji...@apache.org> on 2018/01/10 14:40:00 UTC
[jira] [Commented] (IGNITE-6946) Change Ignite Logger configuration
on the fly
[ https://issues.apache.org/jira/browse/IGNITE-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320344#comment-16320344 ]
Alexey Popov commented on IGNITE-6946:
--------------------------------------
Could be added to:
https://cwiki.apache.org/confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime
> 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
>
> It would be great if we can change Ignite Logger configuration on the fly without restarting the cluster node. I 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
(v6.4.14#64029)