[ https://issues.apache.org/jira/browse/IGNITE-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340231#comment-16340231 ]
Valentin Kulichenko commented on IGNITE-6946: --------------------------------------------- [~slukyanov], I think you should add tests for other loggers as well. Other than that looks good. Also there are some other changes in log4j.xml which I believe are there by accident? If there are done on purpose, can you please explain them? > 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)