You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Alexey Popov (JIRA)" <ji...@apache.org> on 2017/11/17 09:51:00 UTC
[jira] [Created] (IGNITE-6946) Change Ignite Logger configuration
on the fly
Alexey Popov created IGNITE-6946:
------------------------------------
Summary: Change Ignite Logger configuration on the fly
Key: IGNITE-6946
URL: https://issues.apache.org/jira/browse/IGNITE-6946
Project: Ignite
Issue Type: Improvement
Security Level: Public (Viewable by anyone)
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)