ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8951) Need to validate nodes configuration across cluster and warn on different parameters value
Date Mon, 13 Aug 2018 10:28:00 GMT

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

Alexey Goncharuk commented on IGNITE-8951:

Guys, let's provide the list of mandatory matching configuration properties here in the ticket,
this should be added to the documentation as well.

> Need to validate nodes configuration across cluster and warn on different parameters
> ------------------------------------------------------------------------------------------
>                 Key: IGNITE-8951
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8951
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Yakov Zhdanov
>            Priority: Major
> On node start, node should output in its logs the  list of parameters havnig values different
from values on remote node. This should be skipped for parameters that are always different
e.g. host name, node ID or IP, however should be an option to include parameters from default
ignore list as well.
> Another requrement is that the intended output may be fully supressed by setting sysmem
> It seems that the implementation approach should be similar to performance suggestions
Ignite currently has.
> The output may be as following
> {noformat}
> Local node has different configuration comparted to remote nodes for paramenters (fix
>   ^-- rebalanceThreadPoolSize [locNodeVal=4, rmtNodeId=X1X1, rmtNodeVal=8]
>   ^-- commSpi.selectorsCnt [locNodeVal=2, rmtNodeId=Y1Y1, rmtNodeVal=4]
>   ^-- commSpi.selectorsCnt [locNodeVal=2, rmtNodeId=Z1Z1, rmtNodeVal=8]
> {noformat}
> All components should add messages to {{cfgConsistencyRegister}} on startup and then
all differences should be output in one step.
> If node aborts startup due to any problem differences collected so far should be output
to logs.
> If there are more than 1 value for some config parameter among remote nodes then all
distinct options should be output (see {{commSpi.selectorsCnt}} in the example above).

This message was sent by Atlassian JIRA

View raw message