MySQL Bugs: #99745: Slave stops with HA_ERR_KEY_NOT

Bug #99745	Slave stops with HA_ERR_KEY_NOT_FOUND error
Submitted:	29 May 2020 16:13	Modified:	3 Jul 2020 2:35
Reporter:	benedetto lo giudice	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Group Replication	Severity:	S3 (Non-critical)
Version:	8.0.16	OS:	Ubuntu (18.04)
Assigned to:	MySQL Verification Team	CPU Architecture:	x86

Description:
We run a MySql group replication cluster of 3 nodes on Kubernetes.

One node suddenly left the cluster today and we found this error:

May 29 06:43:05 mysql-cluster-0 mysql ERROR [MY-010584] [Repl] Slave SQL for channel 'group_replication_applier': Could not execute Delete_rows event on table myapp.QRTZ_FIRED_TRIGGERS; Can't find record in 'QRTZ_FIRED_TRIGGERS', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND, Error_code: MY-001032

I found a very old bug report: https://bugs.mysql.com/bug.php?id=51501

How to repeat:
Unfortunately this happened while one of the microservices components that interacts with the QRTZ tables was restarting. 
I will try to reproduce but right now I don't have that info.

Suggested fix:
I couldn't find any workaround.
This is a mysql cluster with group replication running in Kubernetes.

Hi,

I doubt that bug is related (and it was fixed many years ago).

I'm sorry but I don't have enough data to proceed with this report. No idea how it happened and no way to reproduce it. No idea even what to try to do to reproduce it.

kind regards

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Please show us output of:

SHOW CREATE TABLE myapp.QRTZ_FIRED_TRIGGERS;

we want to know if that table has a primary key or not.