[MDEV-30769] InnoDB Clustered record for sec rec not found index Created: 2023-03-02  Updated: 2023-07-06  Resolved: 2023-07-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.28
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: zhangxiaohua Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, index, innodb


 Description   

2023-03-02 10:55:12 51 [ERROR] InnoDB: Clustered record for sec rec not found index `problem_1` of table `zabbix`.`problem`
InnoDB: sec index record PHYSICAL RECORD: n_fields 4; compact format; info bits 0
0: len 4; hex 80000000; asc ;;
1: len 4; hex 80000000; asc ;;
2: len 8; hex 000000000000c1fe; asc ;;
3: len 8; hex 0000000002c21dec; asc ;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 16; compact format; info bits 0
0: len 8; hex 0000000002bb364c; asc 6L;;
1: len 6; hex 000000000000; asc ;;
2: len 7; hex 80000000000000; asc ;;
3: len 4; hex 80000000; asc ;;
4: len 4; hex 80000000; asc ;;
5: len 8; hex 00000000000091b1; asc ;;
6: len 4; hex e224294f; asc $)O;;
7: len 4; hex ab62e736; asc b 6;;
8: SQL NULL;
9: len 4; hex 80000000; asc ;;
10: len 4; hex 80000000; asc ;;
11: SQL NULL;
12: SQL NULL;
13: len 29; hex 496e74657266616365204661302f313628293a204c696e6b20646f776e; asc Interface Fa0/16(): Link down;;
14: len 4; hex 80000000; asc ;;
15: len 4; hex 80000003; asc ;;

TRANSACTION 421956045321576, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 0
0 lock struct(s), heap size 1128, 0 row lock(s)
MySQL thread id 51, OS thread handle 140471920727808, query id 418169 localhost zabbix Sending data
select eventid,objectid from problem where source=0 and object=0 and objectid in (18368,18373,18376,18377,18378,18379,18382,49653,49662,49669,49670) and r_eventid is null

InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

 Comments   
Comment by Daniel Black [ 2023-03-02 ]

For clarify, which MariaDB version?
Can you include output from show create table zabbix.problem?
Which version of MariaDB or MySQL was used when the original table was created?

Comment by zhangxiaohua [ 2023-03-02 ]

MariaDB [(none)]> status;
--------------
mysql Ver 15.1 Distrib 10.3.28-MariaDB, for Linux (x86_64) using readline 5.1

Connection id: 5398
Current database:
Current user: root@localhost
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server: MariaDB
Server version: 10.3.28-MariaDB MariaDB Server
Protocol version: 10
Connection: Localhost via UNIX socket
Server characterset: latin1
Db characterset: latin1
Client characterset: utf8
Conn. characterset: utf8
UNIX socket: /var/lib/mysql/mysql.sock
Uptime: 3 hours 30 min 31 sec

Threads: 133 Questions: 877949 Slow queries: 1393 Opens: 459 Flush tables: 1 Open tables: 452 Queries per second avg: 69.507

Comment by zhangxiaohua [ 2023-03-02 ]

MariaDB [(none)]> show create table zabbix.problem;
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Table Create Table

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

problem CREATE TABLE `problem` (
`eventid` bigint(20) unsigned NOT NULL,
`source` int(11) NOT NULL DEFAULT 0,
`object` int(11) NOT NULL DEFAULT 0,
`objectid` bigint(20) unsigned NOT NULL DEFAULT 0,
`clock` int(11) NOT NULL DEFAULT 0,
`ns` int(11) NOT NULL DEFAULT 0,
`r_eventid` bigint(20) unsigned DEFAULT NULL,
`r_clock` int(11) NOT NULL DEFAULT 0,
`r_ns` int(11) NOT NULL DEFAULT 0,
`correlationid` bigint(20) unsigned DEFAULT NULL,
`userid` bigint(20) unsigned DEFAULT NULL,
`name` varchar(2048) COLLATE utf8_bin NOT NULL DEFAULT '',
`acknowledged` int(11) NOT NULL DEFAULT 0,
`severity` int(11) NOT NULL DEFAULT 0,
PRIMARY KEY (`eventid`),
KEY `problem_1` (`source`,`object`,`objectid`),
KEY `problem_2` (`r_clock`),
KEY `problem_3` (`r_eventid`),
CONSTRAINT `c_problem_1` FOREIGN KEY (`eventid`) REFERENCES `events` (`eventid`) ON DELETE CASCADE,
CONSTRAINT `c_problem_2` FOREIGN KEY (`r_eventid`) REFERENCES `events` (`eventid`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.038 sec)

MariaDB [(none)]>

Comment by Daniel Black [ 2023-07-06 ]

With 10.3 EOL I don't think there's much we can do. There's nothing to repeat the problem.

You can remove and recreate the index to resolve the errors, which I assume you have done.

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