MySQL Replication issue

[Beekshan Chaki]

We are using MySQL Community Server version 8.0.45 for a database with a total data size more than 20 TB. Our setup includes a DC–DR replication using MySQL native replication. We are also using table partitioning.

During replication, we are encountering the following errors:

* *Error Code: 1030* – Got error -1 from storage engine
* *Error Code: 1032* – Can't find record in table

We have tested both binlog-based and GTID-based replication, and the issue persists in both configurations.

Notably:

* There were no network interruptions during the incidents.
* No corresponding OS-level errors were observed.

We are trying to understand the root cause of these errors in a large, partitioned environment and how to resolve them without risking data inconsistency.

Any guidance on possible causes and recommended troubleshooting steps would be greatly appreciated.

Thank you.