Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

innodb_redo_log_encrypt does not behave correctly with SET PERSIST_ONLY

Description

While testing PR-4556, below Scenario was executed:

Start the server with innodb_redo_log_encrypt=keyring_key
set persist_only innodb_redo_log_encrypt=master_key;
shutdown;
try to restart the server
In ideal scenario, the server should not come up because the redo logs are encrypted with keyring_key
But, currently the server starts and if we select the value of innodb_redo_log_encrypt, it is shown as OFF

Environment

None

Smart Checklist

Activity

Zsolt Parragi July 26, 2019 at 8:23 AM

Upstream only has ON/OFF, so it's not an issue for them.

Laurynas Biveinis July 26, 2019 at 8:22 AM

What is upstream status, with upstream allowed values for innodb_redo_log_encrypt?

Done

Details

Assignee

Reporter

Labels

Time tracking

2h logged

Fix versions

Affects versions

Priority

Smart Checklist

Created July 25, 2019 at 12:21 PM
Updated March 6, 2024 at 11:59 AM
Resolved August 1, 2019 at 9:17 AM

Flag notifications