ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup
Date Fri, 20 Jul 2018 07:32:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550331#comment-16550331

ASF GitHub Bot commented on IGNITE-5798:

Github user 1vanan closed the pull request at:


> 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
>            Priority: Major
>              Labels: easyfix, newbie
>             Fix For: 2.5
> 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

View raw message