ID | IEP-52 |
Author | |
Sponsor | |
Created |
|
Status | DRAFT |
Currently, Apache Ignite is being shipped as single monolith binary with lots of excess modules and libs, majority of which are not required in most use case scenarios.
Also, current upgrade process is too tied to binary delivery, requiring users to copy working directory, additional libs and other configurations between version upgrades, which is rather error prone.
This IEP targets to solve both problems the following way:
Final target – recreate binary delivery in a way, that will allow user to upgrade Apache Ignite instance with only downloading a new binary and executing the same ignite.sh command from new version.
Redesign binary assembly to prepare at least 2 archives:
bin
, config
, libs
(without optional)apache-ignite-extras with all other additional files: benchmarks
, docs
, examples
, platform
Replace shipping of optional libs via including Maven-powered dependency management.
Update Apache Ignite configuration via configuration files to support external files (outside IGNITE_HOME) with external paths (outside IGNITE_HOME too) to persisted between version upgrades directories (work
, log
, etc.)
Proposed changes will require one time re-setup of Apache Ignite instance as well as constructing updated ignite.sh run command.
Next version upgrade will require only running the same ignite.sh run command from new version binary.
Development list: IEP-52: Binary Delivery & Upgradability Enhancements
n/a
n/a