Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
Description
The key rotation checks process done by the background encryption threads can be quite CPU intensive. See MDEV-10368 and MDEV-11581 for some examples of some previous performance issues caused by key rotation.
Would it be worth adding a new configuration variable to disable key rotations for users who do not need it, but who still need to set innodb_encryption_treads > 0?
Attachments
Issue Links
- relates to
-
MDEV-14398 When innodb_encryption_rotate_key_age=0 is set, server won't encrypt tablespaces
- Closed