[jira] [Updated] (IGNITE-5798) Logging Ignite configuration at startup
[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-5798: --- Fix Version/s: (was: 2.3) > Logging Ignite configuration at startup > --- > > Key: IGNITE-5798 > URL: https://issues.apache.org/jira/browse/IGNITE-5798 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr Kuramshin >Assignee: Ivan Fedotov > Labels: easyfix, newbie > > I've found that IgniteConfiguration is not logged even when > -DIGNITE_QUIET=false > When we starting Ignite with path to the xml, or InputStream, we have to > ensure, that all configuration options were properly read. And also we would > like to know actual values of uninitialized configuration properties (default > values), which will be set only after Ignite get started. > Monitoring tools, like Visor or WebConsole, do not show all configuration > options. And even though they will be updated to show all properties, when > new configuration options appear, then tools update will be needed. > Logging IgniteConfiguration at startup gives a possibility to ensure that the > right grid configuration has been applied and leads to better user support > based on log analyzing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5798) Logging Ignite configuration at startup
[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-5798: - Fix Version/s: (was: 2.1) 2.2 > Logging Ignite configuration at startup > --- > > Key: IGNITE-5798 > URL: https://issues.apache.org/jira/browse/IGNITE-5798 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr Kuramshin > Labels: easyfix, newbie > Fix For: 2.2 > > > I've found that IgniteConfiguration is not logged even when > -DIGNITE_QUIET=false > When we starting Ignite with path to the xml, or InputStream, we have to > ensure, that all configuration options were properly read. And also we would > like to know actual values of uninitialized configuration properties (default > values), which will be set only after Ignite get started. > Monitoring tools, like Visor or WebConsole, do not show all configuration > options. And even though they will be updated to show all properties, when > new configuration options appear, then tools update will be needed. > Logging IgniteConfiguration at startup gives a possibility to ensure that the > right grid configuration has been applied and leads to better user support > based on log analyzing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5798) Logging Ignite configuration at startup
[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-5798: Labels: easyfix newbie (was: easyfix) > Logging Ignite configuration at startup > --- > > Key: IGNITE-5798 > URL: https://issues.apache.org/jira/browse/IGNITE-5798 > Project: Ignite > Issue Type: Improvement >Reporter: Alexandr Kuramshin > Labels: easyfix, newbie > Fix For: 2.1 > > > I've found that IgniteConfiguration is not logged even when > -DIGNITE_QUIET=false > When we starting Ignite with path to the xml, or InputStream, we have to > ensure, that all configuration options were properly read. And also we would > like to know actual values of uninitialized configuration properties (default > values), which will be set only after Ignite get started. > Monitoring tools, like Visor or WebConsole, do not show all configuration > options. And even though they will be updated to show all properties, when > new configuration options appear, then tools update will be needed. > Logging IgniteConfiguration at startup gives a possibility to ensure that the > right grid configuration has been applied and leads to better user support > based on log analyzing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
