My Oracle Support Banner

HA_ERR_KEY_NOT_FOUND On Innodb Replica in InnoDB Cluster (Doc ID 2817076.1)

Last updated on OCTOBER 25, 2021

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Symptoms

On : 8.0 version, Server Crash

HA_ERR_KEY_NOT_FOUND on Innodb replica
This happened to two nodes in our cluster and our cluster was unable to process transactions

ERROR
-----------------------
Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND, Error_code: MY-001032


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set the binlog_row_image=MINIMAL system variables.
2. Create a table with a generated column.
3. Attempt to DELETE/UPDATE the table.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get consistent, durable data.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.