# Issue with GTID enabled MySQL 5.6.10

**URL:** <https://forums.percona.com/t/issue-with-gtid-enabled-mysql-5-6-10/3566>\
**Category:** Other MySQL® Questions\
**Created:** [June 24, 2014, 9:16am UTC](https://forums.percona.com/t/issue-with-gtid-enabled-mysql-5-6-10/3566 "2014-06-24T09:16:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sysad](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@sysad](https://forums.percona.com/u/sysad)\
**Post date:** [June 24, 2014, 9:16am UTC](https://forums.percona.com/t/issue-with-gtid-enabled-mysql-5-6-10/3566/1 "2014-06-24T09:16:36Z")

</div>

Hi Folks

In order to introduce MySQL 5.6 with GTID to an existing cluster, I built a slave running a patched version of mysql Ver 14.14 Distrib 5.6.10, for Linux (x86\_64) , which does not check if GTID is enabled on the master running Percona 5.5 (mysql Ver 14.14 Distrib 5.5.28, for Linux (x86\_64)

The patched slave was built by taking a mysql dump of all the databases from the existing cluster.

This patched slave ran for a few days without issues, apart from a few errors in the log

============================  
34551 [ERROR] Native table ‘performance\_schema’.‘cond\_instances’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_current’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_history’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_history\_long’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_summary\_by\_host\_by\_event\_name’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_summary\_by\_instance’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_summary\_by\_thread\_by\_event\_name’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_summary\_by\_user\_by\_event\_name’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_summary\_by\_account\_by\_event\_name’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘events\_waits\_summary\_global\_by\_event\_name’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘file\_instances’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘file\_summary\_by\_event\_name’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘file\_summary\_by\_instance’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘host\_cache’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘mutex\_instances’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘objects\_summary\_global\_by\_type’ has the wrong structure  
34551 [ERROR] Native table ‘performance\_schema’.‘performance\_timers’ has the wrong structure

…

============================

and after 4-5 days, more errors were introduced into the error log

=============================  
7fb3a491c700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a491c700 InnoDB: Error: Fetch of persistent statistics requested for table “xyz\_ddb”.“StaticPages” but the required system tables mysql.innodb\_table\_stats and mysql.innodb\_index\_stats are not present or have unexpected structure. Using  
7fb3a491c700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a491c700 InnoDB: Error: Fetch of persistent statistics requested for table “xyz\_ugc”.“authors” but the required system tables mysql.innodb\_table\_stats and mysql.innodb\_index\_stats are not present or have unexpected structure. Using  
7fb3a491c700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a491c700 InnoDB: Error: Fetch of persistent statistics requested for table “xyzSEO”.“queries” but the required system tables mysql.innodb\_table\_stats and mysql.innodb\_index\_stats are not present or have unexpected structure. Using  
7fb3a491c700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a491c700 InnoDB: Error: Fetch of persistent statistics requested for table “xyzSEO”.“stores” but the required system tables mysql.innodb\_table\_stats and mysql.innodb\_index\_stats are not present or have unexpected structure. Using  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “xyz\_moderation”.“entity\_states” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “xyz\_ugc”.“review\_summary\_sources” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “xyz\_ugc”.“review\_summary\_sources” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “xyz\_ugc”.“review\_summary” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “xyz\_ugc”.“review\_summary\_sources” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
7fb3a491c700 InnoDB: Error: Fetch of persistent statistics requested for table “xyz”.“W3\_CONSOLE\_PRIVS” but the required system tables mysql.innodb\_table\_stats and mysql.innodb\_index\_stats are not present or have unexpected structure. Using transient stats instead.

…

7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “analytics”.“ORDERS” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead  
7fb3a5980700 InnoDB: Error: Table “mysql”.“innodb\_table\_stats” not found.  
44978 [Note] Error reading relay log event: slave SQL thread was killed  
44978 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server\_errno=2013)  
44978 [Note] Slave I/O thread killed while reading event  
[B]44978 [Note] Slave I/O thread exiting, read up to log ‘www-db01-bin.018891’, position 539176249  
…  
44978 [ERROR] Error in Log\_event::read\_log\_event(): ‘Event too big’, data\_len: 1929577984, event\_type: 32  
44978 [Warning] Error reading GTIDs from binary log: -1​

# … 44978 [ERROR] Error in Log\_event::read\_log\_event(): ‘Sanity check failed’, data\_len: 976630074, event\_type: 58[/B] 44978 [Warning] Error reading GTIDs from binary log: -1

and finally mysqld crashed over this error and I have not been able to start it up again.

=============================

7fb3a5980700 InnoDB: Recalculation of persistent statistics requested for table “analytics”.“ORDERS” but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.  
10:20:06 UTC - mysqld got signal 11 ;  
This could be because you hit a bug. It is also possible that this binary  
or one of the libraries it was linked against is corrupt, improperly built,  
or misconfigured. This error can also be caused by malfunctioning hardware.  
We will try our best to scrape up some info that will hopefully help  
diagnose the problem, but since we have already crashed,  
something is definitely wrong and this may fail.  
key\_buffer\_size=33554432  
read\_buffer\_size=131072  
max\_used\_connections=2  
max\_threads=5000  
thread\_count=2  
connection\_count=0  
It is possible that mysqld could use up to  
key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 2020346 K bytes of memory  
Hope that’s ok; if not, decrease some variables in the equation.  
Thread pointer: 0x5d0bf1c0  
Attempting backtrace. You can use the following information to find out  
where mysqld died. If you see no messages after this, something went  
terribly wrong…  
stack\_bottom = 7fb3a491b9d0 thread\_stack 0x30000  
/usr/local/mysql/bin/mysqld(my\_print\_stacktrace+0x2e)[0x8a7ffe]  
/usr/local/mysql/bin/mysqld(handle\_fatal\_signal+0x481)[0x68f801]  
/lib/x86\_64-linux-gnu/libpthread.so.0(+0xf030)[0x7fc21ea73030]  
/usr/local/mysql/bin/mysqld[0x6a6c1d]  
/usr/local/mysql/bin/mysqld(\_Z11mysql\_grantP3THDPKcR4ListI11st\_lex\_userEmbb+0x4b9)[0x6b0a09]  
/usr/local/mysql/bin/mysqld(\_Z21mysql\_execute\_commandP3THD+0x3489)[0x6fab89]  
/usr/local/mysql/bin/mysqld(\_Z11mysql\_parseP3THDPcjP12Parser\_state+0x388)[0x6fbe58]  
/usr/local/mysql/bin/mysqld(\_ZN15Query\_log\_event14do\_apply\_eventEPK14Relay\_log\_infoPKcj+0x661)[0x84d821]  
/usr/local/mysql/bin/mysqld(\_ZN9Log\_event11apply\_eventEP14Relay\_log\_info+0x67)[0x84c147]  
/usr/local/mysql/bin/mysqld(\_Z26apply\_event\_and\_update\_posPP9Log\_eventP3THDP14Relay\_log\_info+0x1a6)[0x877446]  
/usr/local/mysql/bin/mysqld(handle\_slave\_sql+0x9e6)[0x879d96]  
/usr/local/mysql/bin/mysqld(pfs\_spawn\_thread+0x16f)[0x92a06f]  
/lib/x86\_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7fc21ea6ab50]  
/lib/x86\_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc21d7d10ed]

Trying to get some variables.  
Some pointers may be invalid and cause the dump to abort.  
Query (7fb39c03b30f): is an invalid pointer  
Connection ID (thread ID): 32  
Status: NOT\_KILLED

# The manual page at [http://dev.mysql.com/doc/mysql/en/crashing.html](http://dev.mysql.com/doc/mysql/en/crashing.html) contains information that should help you find out what is causing the crash. 140620 15:50:11 mysqld\_safe Number of processes running now: 0

and I have another non GTID 5.6 slave in the same cluster with the version (mysql Ver 14.14 Distrib 5.6.15, for Linux (x86\_64)) running without issues.

Could someone help me here in understanding what could have been the issue with the GTID slave ?

P.S : The GTID enabled slave was built by compiling from source and commenting the lines that check whether the master is GTID enabled.

Regards  
sysad

---

<div class="post-metadata">

**Author:** ![yogesh777](https://avatars.discourse-cdn.com/v4/letter/y/87869e/32.png) [@yogesh777](https://forums.percona.com/u/yogesh777)\
**Post date:** [July 7, 2014, 11:27pm UTC](https://forums.percona.com/t/issue-with-gtid-enabled-mysql-5-6-10/3566/2 "2014-07-07T23:27:34Z")

</div>

either your disk/storage is 100% utilized or system tables get corrupted, rebuilding mysql schema structure might help you.
