[IGNITE-19911] Initial cluster configuration should be validated against the default configuration

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Labels: ignite-3
• Epic Link: Configuration improvements
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Kirill Sizov
• Reporter: Ivan Gagarkin
• Created: 04/Jul/23 10:37
• Updated: 08/Aug/23 13:59

Description

Users can set a custom cluster configuration on init. That configuration is validated against an empty configuration. It's not correct because the cluster is initialized with the default configuration first, and then a custom configuration is applied. 

 

For example, if a user changes immutable properties in the custom cluster configuration on the cluster init. This configuration is successfully validated before the initialization process and the initialization is started. But when the initialization is passed and the cluster leader tries to apply the custom configuration, it fetches the error that immutable parameters can not be changed. 

Issue Links

• is related to: IGNITE-19792 Support @Immutable logic for distributed configuration