• Motivation
• Description
• Risks and Assumptions
• Discussion Links
• Reference Links
• Tickets

Motivation

The current approach for Ignite configuration was formed a long time ago (originally inherited from GridGain during the project donation) and has several disadvantages that manifested themselves over time as project gained more usage across different users. There are several orthogonal aspects that need to be addressed.

...

Dynamic cache configuration persistence depends on whether the cache is persistent or not. A memory-only dynamic cache will not be recreated on a cluster restart (even if there are other persistent caches), while persistent caches are preserved. 

Description

The purpose of this IEP is to provide a revisited unified approach to configuring an Ignite cluster, which addresses the issues stated above by achieving the following goals:

...

ignitectl -node consistent_id node.rebalance.threads=4

Similarly, the tool can read property or the whole subtree value, export properties to a file or even update the cluster configuration based on a file.

#read the property value
ignitectl cluster.baseilne.auto-adjust.timeout

#write values from the config file
ignitectl -w custom.properties

#update local properties on on all nodes in current topology
ignitectl -node * node.rebalance.threads=4

Risks and Assumptions

New configuration approach will require more effort from existing users during migration. Additionally, it will require a thorough configuration revisit and clear separation of global and local properties.

Discussion Links

TBD

Reference Links

1. https://github.com/lightbend/config

Tickets