[IGNITE-14424] Cache group re-encryption does not start after cluster secondary activation.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10
• Fix Version/s: 2.11
• Release Note: Fixed cache group re-encryption after cluster secondary activation
• Ignite Flags: Release Notes Required
• Assignee: Pavel Pereslegin
• Reporter: Pavel Pereslegin
• Created: 26/Mar/21 09:06
• Updated: 30/Jun/21 07:32
• Resolved: 04/Jun/21 13:48

Description

Cache group re-encryption does not start after cluster secondary activation.

Reproducer

    @Test
    public void testDeactivation() throws Exception {
        pageScanRate = 2;
        checkpointFreq = 10;

        T2<IgniteEx, IgniteEx> nodes = startTestGrids(true);

        IgniteEx node0 = nodes.get1();
        IgniteEx node1 = nodes.get2();

        createEncryptedCache(node0, node1, cacheName(), null);

        loadData(100_000);

        node0.encryption().changeCacheGroupKey(Collections.singleton(cacheName())).get();

        assertTrue(isReencryptionInProgress(Collections.singleton(cacheName())));

        node0.cluster().state(ClusterState.INACTIVE);

        assertFalse(isReencryptionInProgress(Collections.singleton(cacheName())));

        node0.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);
        node1.context().encryption().setReencryptionRate(DFLT_REENCRYPTION_RATE_MBPS);

        node0.cluster().state(ClusterState.ACTIVE);

        checkGroupKey(CU.cacheId(cacheName()), INITIAL_KEY_ID + 1, MAX_AWAIT_MILLIS); // failing here
    }

Issue Links

• causes: IGNITE-14894 Ignite RDD test suite is broken
• relates to: IGNITE-12843 TDE - Phase-3. Cache key rotation.
• links to: GitHub Pull Request #9036
• links to: TC run all