[MDEV-30600] Hit a bug that the error log says I should report Created: 2023-02-07  Updated: 2023-03-27  Resolved: 2023-03-27

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.22
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Richard Jans Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash


 Description   

Here is the data from the error log:

2023-02-07  9:47:39 1263 [ERROR] InnoDB: Clustered record for sec rec not found index `cf_data_collection_object_id_v_string_idx` of table `service_desk`.`cf_data_collection`
InnoDB: sec index record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
 0: len 4; hex 807d1728; asc  } (;;
 1: len 18; hex 804f12910000000000000000000000000000; asc  O                ;;
 2: len 4; hex 00000000; asc     ;;
 
InnoDB: clust index record PHYSICAL RECORD: n_fields 1; compact format; info bits 0
 0: len 8; hex 696e66696d756d00; asc infimum ;;
 
TRANSACTION 421748213171280, ACTIVE 14 sec starting index read, thread declared inside InnoDB 4261
mysql tables in use 6, locked 0
0 lock struct(s), heap size 1136, 0 row lock(s)
MySQL thread id 1263, OS thread handle 140267557455616, query id 16344 10.20.11.31 desk_user Sending data
SELECT COUNT( DISTINCT `olap_incident_facts`.`incident`) AS `_ac0` FROM `olap_incident_facts`
 LEFT JOIN (SELECT `data_table`.`object_id`, `data_table`.`v_string` AS `value` FROM `cf_data_collection` AS `data_table`
 INNER JOIN `cf_fields` AS `cfs` ON data_table.field_id = cfs.id WHERE (data_table.v_string IS NOT NULL) AND (data_table.v_string != '') AND (cfs.id = 55) AND (data_table.status = 1) GROUP BY `data_table`.`object_id`,
        `data_table`.`v_string`) AS `view_olap_snowflake_55` ON `view_olap_snowflake_55`.`object_id` = `olap_incident_facts`.`incident`
 LEFT JOIN (SELECT DISTINCT `data_tab
 
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

Server version: MariaDB-server-10.3.22-1.el7.centos.x86_64 (it's an rpm name)



 Comments   
Comment by Sergei Golubchik [ 2023-02-27 ]

10.3.22 is quite old (Jan 2020), and 10.3 is almost reached its end of life.

Could you try to see if this happens at least in 10.4?

Generated at Thu Feb 08 10:17:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.