Bug #98564 | [InnoDB] Assertion failure: space->encryption_op_in_progress == NONE | ||
---|---|---|---|
Submitted: | 12 Feb 2020 10:28 | Modified: | 17 Feb 2021 11:01 |
Reporter: | Satya Bodapati (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0, 8.0.19 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[12 Feb 2020 10:28]
Satya Bodapati
[12 Feb 2020 10:29]
Satya Bodapati
mtr testcase
Attachment: ddl_log_issue.test (application/octet-stream, text), 3.83 KiB.
[12 Feb 2020 10:32]
Satya Bodapati
code change. sleep
Attachment: ddl_log_code_change.diff (text/x-patch), 555 bytes.
[12 Feb 2020 11:45]
MySQL Verification Team
Hello Satya, Thank you for the report and feedback! regards, Umesh
[12 Feb 2020 13:16]
MySQL Verification Team
I think that debug patch is fine, since it only introduces sleep() when server is compiled with full debug info.
[17 Sep 2020 16:27]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.23 release, and here's the proposed changelog entry from the documentation team: An interrupted tablespace encryption operation did not update the encrypt_type table option information in the data dictionary when the operation resume processing after the server was restarted.
[21 Sep 2020 16:35]
MySQL Verification Team
Thank you, Daniel.
[15 Feb 2021 8:59]
Satya Bodapati
Thank you for fixing this! This should be in closed status though.
[15 Feb 2021 13:44]
MySQL Verification Team
Hi, We agree with Mr. Bodapati that this report should be closed.
[17 Feb 2021 11:01]
Erlend Dahl
In response to urgent requests from Mr Bodapati and Mr Milivojevic, I close the bug.