Hitesh Mundra

May 8, 2015 21:57
welcome :)
May 8, 2015 21:51
Your table data size is more than innodb_buffer_pool (which is store in ram). means need lot of disk read/write IO. It takes time more than lock_timeout.
May 8, 2015 21:30
your innodb_buffer_pool_size variable is not set correctly. Its value lie 70-80 % of RAM. As RIBPS result, minimum it should be 4GB. but above message it shows 2.1 GB (Total memory allocated 2125824000) . set it & run the transaction
May 8, 2015 21:08
what's your RAM size
May 8, 2015 21:07
what results ?
May 8, 2015 21:07
run the query- SELECT CEILING(Total_InnoDB_Bytes*1.6/POWER(1024,3)) RIBPS FROM
(SELECT SUM(data_length+index_length) Total_InnoDB_Bytes
FROM information_schema.tables WHERE engine='InnoDB') A;
May 8, 2015 20:43
what about BUFFER POOL AND MEMORY section
May 8, 2015 20:22
what's the output of SHOW ENGINE INNODB STATUS\G
May 8, 2015 20:20
run SHOW ENGINE INNODB STATUS\G & see result, for more detail to understand- dev.mysql.com/doc/refman/5.0/en/innodb-monitors.html
May 8, 2015 20:20
set @@profiling=1; enter the query ; show profile; see what output, where time goes
May 8, 2015 20:20
set profiling variable & see where the time is consuming by show profile commad. it may be possible that after update mysql to 5.6 your server variable untuned, so check server variable