Increased mariadb load and errors in logs

Issue

• We're observing increased Mariadb load of ~20 whereas load around ~8 is expected. The log is flooded by errros:

InnoDB: clust index record PHYSICAL RECORD: n_fields 55; compact format; info bits 0
 0: len 4; hex 81251719; asc  %  ;;
 1: len 6; hex 000000000000; asc       ;;
 2: len 7; hex 80000000000000; asc        ;;
 3: len 5; hex 99adcaa786; asc      ;;
 4: len 5; hex 99adcaa977; asc     w;;
 5: SQL NULL;
 6: SQL NULL;
 7: len 30; hex 656661326266373836323135343634653934663764633563656230373732; asc efa2bf786215464e94f7dc5ceb0772; (total 32 bytes);
 8: len 30; hex 666530353739313433626261343761653835303162356336633765383038; asc fe0579143bba47ae8501b5c6c7e808; (total 32 bytes);
 9: len 30; hex 36356536323133362d376138652d346466662d393166362d356531626431; asc 65e62136-7a8e-4dff-91f6-5e1bd1; (total 36 bytes);
 10: len 0; hex ; asc ;;
 11: len 0; hex ; asc ;;
 12: len 4; hex 80000000; asc     ;;
 13: SQL NULL;
 14: SQL NULL;
 15: len 4; hex 80000000; asc     ;;
 16: len 5; hex 6572726f72; asc error;;
 17: len 4; hex 80001000; asc     ;;
 18: len 4; hex 80000002; asc     ;;
 19: len 13; hex 746573742d6b61696f2d736c69; asc test-kaio-sli;;
 20: SQL NULL;
 21: SQL NULL;
 22: len 10; hex 722d6f39316a387a7338; asc r-o91j8zs8;;
 23: SQL NULL;
 24: SQL NULL;
 25: len 13; hex 746573742d6b61696f2d736c69; asc test-kaio-sli;;
 26: SQL NULL;
 27: SQL NULL;
 28: len 1; hex 80; asc  ;;
 29: SQL NULL;
 30: SQL NULL;
 31: len 4; hex 80000024; asc    $;;
 32: SQL NULL;
 33: len 30; hex 63303966643736342d366634382d343336362d613862332d666339623636; asc c09fd764-6f48-4366-a8b3-fc9b66; (total 36 bytes);
 34: SQL NULL;
 35: SQL NULL;
 36: SQL NULL;
 37: SQL NULL;
 38: len 0; hex ; asc ;;
 39: SQL NULL;
 40: SQL NULL;
 41: SQL NULL;
 42: len 4; hex 80000000; asc     ;;
 43: len 1; hex 80; asc  ;;
 44: len 1; hex 80; asc  ;;
 45: len 1; hex 80; asc  ;;
 46: len 4; hex 80000028; asc    (;;
 47: len 4; hex 80000000; asc     ;;
 48: SQL NULL;
 49: SQL NULL;
 50: len 4; hex 80000000; asc     ;;
 51: SQL NULL;
 52: len 4; hex 80000000; asc     ;;
 53: SQL NULL;
 54: len 1; hex 80; asc  ;;

TRANSACTION 421828740845080, ACTIVE 0 sec fetching rows
mysql tables in use 10, locked 0
0 lock struct(s), heap size 1128, 0 row lock(s)
MySQL thread id 1501329, OS thread handle 140357458220800, query id 2859457598 172.16.21.72 nova Creating sort index
SELECT anon_1.instances_created_at AS anon_1_instances_created_at, anon_1.instances_updated_at AS anon_1_instances_updated_at, anon_1.instances_deleted_at AS anon_1_instances_deleted_at, anon_1.instances_deleted AS anon_1_instances_deleted, anon_1.instances_id AS anon_1_instances_id, anon_1.instances_user_id AS anon_1_instances_user_id, anon_1.instances_project_id AS anon_1_instances_project_id, anon_1.instances_image_ref AS anon_1_instances_image_ref, anon_1.instances_kernel_id AS anon_1_instances_kernel_id, anon_1.instances_ramdisk_id AS anon_1_instances_ramdisk_id, anon_1.instances_hostname

InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2023-06-05 14:41:50 1501251 [ERROR] InnoDB: Clustered record for sec rec not found index `instances_project_id_deleted_idx` of table `nova_cell0`.`instances`
InnoDB: sec index record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 30; hex 666530353739313433626261343761653835303162356336633765383038; asc fe0579143bba47ae8501b5c6c7e808; (total 32 bytes);
 1: len 4; hex 80000000; asc     ;;
 2: len 4; hex 81253331; asc  %31;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 55; compact format; info bits 0
 0: len 4; hex 81251719; asc  %  ;;