[
https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196684#comment-16196684
]
Vladislav Pyatkov commented on IGNITE-5798:
-------------------------------------------
Hi,
Just I have faced with the same issue.
I can not able to verify "WAL history size" after grid is had been started.
We should to show this configuration at start (may by only if it is different
from default).
{{org.apache.ignite.configuration.PersistentStoreConfiguration#walHistSize}}
> 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)
