mysql 索引 崩溃_MySQL 表索引损坏致 Crash？来看看如何修复吧~

……………………………………(大量相同的报错)…………………………………………

2017-08-31T11:11:04.291424Z32394522[ERROR]InnoDB:Recordinindex`t_idx`of table`$db_name`.`$tb_name`wasnotfound on update:TUPLE(info_bits=0,9fields):{[12]121098369601(0x010201000908030609060001),[9](0x000000000000010000),[4]KOWA(0x0B0F0701),[4]AYNA(0x01090E01),[6]STAT44(0x030401040404),[4]AYNA(0x01090E01),[1]0(0x00),[1]0(0x00),[32]8f2a39b44fe74cd781527d856342d834(0x0806020103090204040605070403040708010502070408050603040204080304)}at:COMPACT RECORD(info_bits=0,9fields):{[12]121098369601(0x010201000908030609060001),[9](0x000000000000010000),[4]KOWA(0x0B0F0701),[4]AYNA(0x01090E01),NULL,NULL,[1]0(0x00),[1]0(0x00),[32]8f2a39b44fe74cd781527d856342d834(0x0806020103090204040605070403040708010502070408050603040204080304)}

2017-08-31T03:11:04.291454Z32394522[Note]InnoDB:GIS MBR INFO:1.31506e-47and1.02964e-71,2.8816e-306,1.93059e+53

2017-08-3103:11:040x7fcaf04be700InnoDB:Assertionfailureinthread140509591627520infile row0ins.cc line282

InnoDB:Failingassertion:!cursor->index->is_committed()

InnoDB:Weintentionally generate a memory trap.

InnoDB:Submita detailed bug report to http://bugs.mysql.com.

InnoDB:Ifyougetrepeated assertion failuresorcrashes,even

InnoDB:immediately after the mysqld startup,there may be

InnoDB:corruptionintheInnoDBtablespace.Pleaserefer to

InnoDB:http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html

InnoDB:about forcing recovery.

03:11:04UTC-mysqld got signal6;

Thiscould be because you hit a bug.Itisalso possible thatthisbinary

orone of the libraries it was linked againstiscorrupt,improperly built,

ormisconfigured.Thiserror can also be causedbymalfunctioning hardware.

Attemptingto collect some information that could help diagnose the problem.

Asthisisa crashandsomethingisdefinitely wrong,the information

collection process might fail.

…………………………………………………………………………………………………………

Tryingtogetso