Hello, Andrew. Can you clarify your question?
What checks do you mean, exactly? Do you mean internal Ignite checks or user-provided checks? Ignite checks configuration consistency on node start [1]. Ignite do have consistency check for a joining node. Take a look at [2] and all of it children. [1] https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L825 [2] https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/GridComponent.java#L153 В Ср, 04/07/2018 в 08:58 +0300, Andrew Medvedev пишет: > Hello everybody > > Our company has lots of nodes in cluster, and we have seen some > problems with inconsistent settings on nodes clusterwide. To help us > with this, we made an utility to check consistency of settings on > running cluster, but it is a hack, better ways seems to be settings > validation by each node itself on start/joining topology/etc.. > > 1) Is his needed? > 2) Have the implementation details been discussed somewhere? > > Cheers
signature.asc
Description: This is a digitally signed message part
