MySQL Bugs: #94163: no clust rec is found for a deleted-marked secondary index record.

Bug #94163	no clust rec is found for a deleted-marked secondary index record.
Submitted:	1 Feb 2019 9:52	Modified:	4 Mar 2019 13:24
Reporter:	sun long larry	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S3 (Non-critical)
Version:	5.7.24-log MySQL Community Server	OS:	Red Hat (CentOS Linux release 7.6.1810 (Core))
Assigned to:		CPU Architecture:	x86 (Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz)
Tags:	deleted-marked secondary index record, no clust rec is found

Description:
error log:

2019-01-31T14:31:12.470315Z 82541004 [ERROR] InnoDB: Clustered record for sec rec not found index `zfpt_user_repayment_plan_repay_date_index` of table `capital`.`zfpt_user_repayment_plan`
InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 5; hex 99a2396b6f; asc   9ko;;
 1: len 8; hex 01caed7ab2e610e3; asc    z    ;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 1; compact format; info bits 0
 0: len 8; hex 696e66696d756d00; asc infimum ;;

TRANSACTION 5856343250, ACTIVE 57 sec fetching rows
mysql tables in use 4, locked 0
0 lock struct(s), heap size 1136, 0 row lock(s)
MySQL thread id 82541004, OS thread handle 139732190402304, query id 11466180543 10.40.70.28 bi_db Sending data
select
        mcc.investor_id as 'xxx',
        mcc.capital_id as 'xxx',
        mi.capital_name as 'xxx',
        mcc.sequence_number as 'xxx',
        mcc.id as 'xxx',
        mcr.id as 'xxx',
        mcr.periods as 'xxx',
        mcr.repayment_status as 'xxx',
        tt.repay_status as 'xxx'
        from (
        select zrp.channel_order_no,zrp.repay_status,zrp.period,zrp.channel_product_id
        from db_name.tab_name

InnoDB: Submit a detailed bug report to http://bugs.mysql.com
/usr/local/mysql/bin/mysqld(_ZN18st_select_lex_unit7executeEP3THD+0xbf)[0xd99a7f]
/usr/local/mysql/bin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x34b)[0xd55dab]
/usr/local/mysql/bin/mysqld[0xd167d3]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THDb+0x37ba)[0xd1a25a]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x40d)[0xd1bded]
/usr/local/mysql/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11a5)[0xd1d015]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1dec4]
/usr/local/mysql/bin/mysqld(handle_connection+0x29c)[0xdef52c]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x174)[0xf74ee4]
/lib64/libpthread.so.0(+0x7dd5)[0x7f2bad5f1dd5]
/lib64/libc.so.6(clone+0x6d)[0x7f2bac0aaead]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f14fc3e2520): is an invalid pointer
Connection ID (thread ID): 82540927
Status: NOT_KILLED
 
extra info:

During the time, mysql-server is in a high load and i/o bound.
average load is about: 20
and ssd util keeps: 99%  avgrq-sz: is about 150.

How to repeat:
don't know how to repeat

HI,

You have experienced some corruption. It can be due to hardware problems and due to some temporary glitch in the RAM modules. If you use ECC RAM, 2 bits checking 1 bit correcting, then last option is not possible.

Anyway, we can not proceed without a fully repeatable test case.

Thanks in advance !!!!!

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".