When you change an encryption key for a database, new writes can use the new key straight away. But the data already on disk still needs the old key. Updating that data is a separate job called re-encryption.
Apache Ignite can do this while the cluster serves requests. Cache-group key rotation and background re-encryption were added in Ignite 2.10.0 .
In my test with Ignite 2.18.0, removing the rate limit barely changed the time to finish but application throughput dropped sharply. These notes explain how re-encryption works and how to control its speed.
Which key are we changing?
With persistence and cache encryption enabled, Ignite encrypts stored cache data and its write-ahead log (WAL).
A cache group is a set of caches that share storage structures. Encrypted caches in the same group share a data key. A master key protects those data keys. The TDE documentation describes this setup .
Ignite stores data in fixed-size blocks called pages.…