Re: MYSQL CRASHING FREQUENTLY
Posted by: Sam Mathews
Date: June 29, 2017 07:25AM

Have you confirmed that the crashes occur during the bulk inserts?

Yes. After changing logfile size and log buffer size, when i run bulk insert it crashes in approximate 3 hours.

When i am not running bulk insert it crashes after 10-12 hours.

I am again sending the variable file & logfile

mysql> show global status;

http://textuploader.com/dkah0!

mysql> show engine innodb status\G;

http://textuploader.com/dkah4!

mysql> show variables;
I am sending it in four parts

http://textuploader.com/dkahc! (1/4)

http://textuploader.com/dkahx! (2/4)

http://textuploader.com/dkahg! (3/4)

http://textuploader.com/dkahf! (4/4)



I am also sending the error log file






170629 12:58:21 mysqld_safe Number of processes running now: 0
170629 12:58:21 mysqld_safe mysqld restarted
2017-06-29 12:58:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-06-29 12:58:22 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35-log) starting as process 54072 ...
2017-06-29 12:58:22 54072 [Note] Plugin 'FEDERATED' is disabled.
2017-06-29 12:58:22 54072 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-06-29 12:58:22 54072 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-29 12:58:22 54072 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-29 12:58:22 54072 [Note] InnoDB: Memory barrier is not used
2017-06-29 12:58:22 54072 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-06-29 12:58:22 54072 [Note] InnoDB: Using Linux native AIO
2017-06-29 12:58:22 54072 [Note] InnoDB: Using CPU crc32 instructions
2017-06-29 12:58:22 54072 [Note] InnoDB: Initializing buffer pool, size = 832.0G
2017-06-29 12:58:59 54072 [Note] InnoDB: Completed initialization of buffer pool
2017-06-29 12:59:03 54072 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-29 12:59:03 54072 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7902132543174
2017-06-29 12:59:03 54072 [Note] InnoDB: Database was not shutdown normally!
2017-06-29 12:59:03 54072 [Note] InnoDB: Starting crash recovery.
2017-06-29 12:59:03 54072 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-06-29 12:59:16 54072 [Note] InnoDB: Restoring possible half-written data pages
2017-06-29 12:59:16 54072 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 7902137785856
InnoDB: Doing recovery: scanned up to log sequence number 7902143028736
InnoDB: Doing recovery: scanned up to log sequence number 7902148271616
InnoDB: Doing recovery: scanned up to log sequence number 7902153514496
InnoDB: Doing recovery: scanned up to log sequence number 7902158757376
InnoDB: Doing recovery: scanned up to log sequence number 7902164000256
InnoDB: Doing recovery: scanned up to log sequence number 7902169243136
InnoDB: Doing recovery: scanned up to log sequence number 7902174486016
InnoDB: Doing recovery: scanned up to log sequence number 7902179728896
InnoDB: Doing recovery: scanned up to log sequence number 7902184971776
InnoDB: Doing recovery: scanned up to log sequence number 7902190214656
InnoDB: Doing recovery: scanned up to log sequence number 7902195457536
InnoDB: Doing recovery: scanned up to log sequence number 7902200700416
InnoDB: Doing recovery: scanned up to log sequence number 7902205943296
InnoDB: Doing recovery: scanned up to log sequence number 7902211186176
InnoDB: Doing recovery: scanned up to log sequence number 7902216429056
InnoDB: Doing recovery: scanned up to log sequence number 7902221671936
InnoDB: Doing recovery: scanned up to log sequence number 7902226914816
InnoDB: Doing recovery: scanned up to log sequence number 7902232157696
InnoDB: Doing recovery: scanned up to log sequence number 7902237400576
InnoDB: Doing recovery: scanned up to log sequence number 7902242643456
InnoDB: Doing recovery: scanned up to log sequence number 7902247886336
InnoDB: Doing recovery: scanned up to log sequence number 7902253129216
InnoDB: Doing recovery: scanned up to log sequence number 7902258372096
InnoDB: Doing recovery: scanned up to log sequence number 7902263614976
InnoDB: Doing recovery: scanned up to log sequence number 7902268857856
InnoDB: Doing recovery: scanned up to log sequence number 7902274100736
InnoDB: Doing recovery: scanned up to log sequence number 7902279343616
InnoDB: Doing recovery: scanned up to log sequence number 7902284586496
InnoDB: Doing recovery: scanned up to log sequence number 7902289829376
InnoDB: Doing recovery: scanned up to log sequence number 7902295072256
InnoDB: Doing recovery: scanned up to log sequence number 7902300315136
InnoDB: Doing recovery: scanned up to log sequence number 7902305558016
InnoDB: Doing recovery: scanned up to log sequence number 7902310800896
InnoDB: Doing recovery: scanned up to log sequence number 7902316043776
InnoDB: Doing recovery: scanned up to log sequence number 7902321286656
InnoDB: Doing recovery: scanned up to log sequence number 7902326529536
InnoDB: Doing recovery: scanned up to log sequence number 7902331772416
InnoDB: Doing recovery: scanned up to log sequence number 7902337015296
InnoDB: Doing recovery: scanned up to log sequence number 7902342258176
InnoDB: Doing recovery: scanned up to log sequence number 7902347501056
InnoDB: Doing recovery: scanned up to log sequence number 7902352743936
InnoDB: Doing recovery: scanned up to log sequence number 7902357986816
InnoDB: Doing recovery: scanned up to log sequence number 7902363229696
InnoDB: Doing recovery: scanned up to log sequence number 7902368472576
InnoDB: Doing recovery: scanned up to log sequence number 7902373715456
InnoDB: Doing recovery: scanned up to log sequence number 7902378958336
InnoDB: Doing recovery: scanned up to log sequence number 7902384201216
InnoDB: Doing recovery: scanned up to log sequence number 7902389444096
InnoDB: Doing recovery: scanned up to log sequence number 7902394686976
InnoDB: Doing recovery: scanned up to log sequence number 7902399929856
InnoDB: Doing recovery: scanned up to log sequence number 7902405172736
InnoDB: Doing recovery: scanned up to log sequence number 7902410415616
InnoDB: Doing recovery: scanned up to log sequence number 7902415658496
InnoDB: Doing recovery: scanned up to log sequence number 7902420901376
InnoDB: Doing recovery: scanned up to log sequence number 7902426144256
InnoDB: Doing recovery: scanned up to log sequence number 7902431387136
InnoDB: Doing recovery: scanned up to log sequence number 7902436630016
InnoDB: Doing recovery: scanned up to log sequence number 7902441872896
InnoDB: Doing recovery: scanned up to log sequence number 7902447115776
InnoDB: Doing recovery: scanned up to log sequence number 7902452358656
InnoDB: Doing recovery: scanned up to log sequence number 7902457601536
InnoDB: Doing recovery: scanned up to log sequence number 7902462844416
InnoDB: Doing recovery: scanned up to log sequence number 7902468087296
InnoDB: Doing recovery: scanned up to log sequence number 7902473330176
InnoDB: Doing recovery: scanned up to log sequence number 7902478573056
InnoDB: Doing recovery: scanned up to log sequence number 7902483815936
InnoDB: Doing recovery: scanned up to log sequence number 7902489058816
InnoDB: Doing recovery: scanned up to log sequence number 7902494301696
InnoDB: Doing recovery: scanned up to log sequence number 7902499544576
InnoDB: Doing recovery: scanned up to log sequence number 7902504787456
InnoDB: Doing recovery: scanned up to log sequence number 7902510030336
InnoDB: Doing recovery: scanned up to log sequence number 7902515273216
InnoDB: Doing recovery: scanned up to log sequence number 7902520516096
InnoDB: Doing recovery: scanned up to log sequence number 7902525758976
InnoDB: Doing recovery: scanned up to log sequence number 7902531001856
InnoDB: Doing recovery: scanned up to log sequence number 7902536244736
InnoDB: Doing recovery: scanned up to log sequence number 7902541487616
InnoDB: Doing recovery: scanned up to log sequence number 7902546730496
InnoDB: Doing recovery: scanned up to log sequence number 7902551973376
InnoDB: Doing recovery: scanned up to log sequence number 7902557216256
InnoDB: Doing recovery: scanned up to log sequence number 7902562459136
InnoDB: Doing recovery: scanned up to log sequence number 7902567702016
InnoDB: Doing recovery: scanned up to log sequence number 7902572944896
InnoDB: Doing recovery: scanned up to log sequence number 7902578187776
InnoDB: Doing recovery: scanned up to log sequence number 7902583430656
InnoDB: Doing recovery: scanned up to log sequence number 7902588673536
InnoDB: Doing recovery: scanned up to log sequence number 7902593916416
InnoDB: Doing recovery: scanned up to log sequence number 7902599159296
InnoDB: Doing recovery: scanned up to log sequence number 7902604402176
InnoDB: Doing recovery: scanned up to log sequence number 7902609645056
InnoDB: Doing recovery: scanned up to log sequence number 7902614887936
InnoDB: Doing recovery: scanned up to log sequence number 7902620130816
InnoDB: Doing recovery: scanned up to log sequence number 7902625373696
InnoDB: Doing recovery: scanned up to log sequence number 7902630616576
InnoDB: Doing recovery: scanned up to log sequence number 7902635859456
InnoDB: Doing recovery: scanned up to log sequence number 7902641102336
InnoDB: Doing recovery: scanned up to log sequence number 7902646345216
InnoDB: Doing recovery: scanned up to log sequence number 7902651588096
InnoDB: Doing recovery: scanned up to log sequence number 7902656830976
InnoDB: Doing recovery: scanned up to log sequence number 7902662073856
InnoDB: Doing recovery: scanned up to log sequence number 7902667316736
InnoDB: Doing recovery: scanned up to log sequence number 7902672559616
InnoDB: Doing recovery: scanned up to log sequence number 7902677802496
InnoDB: Doing recovery: scanned up to log sequence number 7902683045376
InnoDB: Doing recovery: scanned up to log sequence number 7902688288256
InnoDB: Doing recovery: scanned up to log sequence number 7902693531136
InnoDB: Doing recovery: scanned up to log sequence number 7902698774016
InnoDB: Doing recovery: scanned up to log sequence number 7902704016896
InnoDB: Doing recovery: scanned up to log sequence number 7902709259776
InnoDB: Doing recovery: scanned up to log sequence number 7902714502656
InnoDB: Doing recovery: scanned up to log sequence number 7902719745536
InnoDB: Doing recovery: scanned up to log sequence number 7902724988416
InnoDB: Doing recovery: scanned up to log sequence number 7902730231296
InnoDB: Doing recovery: scanned up to log sequence number 7902735474176
InnoDB: Doing recovery: scanned up to log sequence number 7902740717056
InnoDB: Doing recovery: scanned up to log sequence number 7902745959936
InnoDB: Doing recovery: scanned up to log sequence number 7902751202816
InnoDB: Doing recovery: scanned up to log sequence number 7902756445696
InnoDB: Doing recovery: scanned up to log sequence number 7902761688576
InnoDB: Doing recovery: scanned up to log sequence number 7902766931456
InnoDB: Doing recovery: scanned up to log sequence number 7902772174336
InnoDB: Doing recovery: scanned up to log sequence number 7902777417216
InnoDB: Doing recovery: scanned up to log sequence number 7902782660096
InnoDB: Doing recovery: scanned up to log sequence number 7902787902976
InnoDB: Doing recovery: scanned up to log sequence number 7902793145856
InnoDB: Doing recovery: scanned up to log sequence number 7902798388736
InnoDB: Doing recovery: scanned up to log sequence number 7902803631616
InnoDB: Doing recovery: scanned up to log sequence number 7902808874496
InnoDB: Doing recovery: scanned up to log sequence number 7902814117376
InnoDB: Doing recovery: scanned up to log sequence number 7902819360256
InnoDB: Doing recovery: scanned up to log sequence number 7902824603136
InnoDB: Doing recovery: scanned up to log sequence number 7902829846016
InnoDB: Doing recovery: scanned up to log sequence number 7902835088896
InnoDB: Doing recovery: scanned up to log sequence number 7902840331776
InnoDB: Doing recovery: scanned up to log sequence number 7902845574656
InnoDB: Doing recovery: scanned up to log sequence number 7902850817536
InnoDB: Doing recovery: scanned up to log sequence number 7902856060416
InnoDB: Doing recovery: scanned up to log sequence number 7902861303296
InnoDB: Doing recovery: scanned up to log sequence number 7902866546176
InnoDB: Doing recovery: scanned up to log sequence number 7902871789056
InnoDB: Doing recovery: scanned up to log sequence number 7902877031936
InnoDB: Doing recovery: scanned up to log sequence number 7902882274816
InnoDB: Doing recovery: scanned up to log sequence number 7902887517696
InnoDB: Doing recovery: scanned up to log sequence number 7902892760576
InnoDB: Doing recovery: scanned up to log sequence number 7902898003456
InnoDB: Doing recovery: scanned up to log sequence number 7902903246336
InnoDB: Doing recovery: scanned up to log sequence number 7902908489216
InnoDB: Doing recovery: scanned up to log sequence number 7902913732096
InnoDB: Doing recovery: scanned up to log sequence number 7902918974976
InnoDB: Doing recovery: scanned up to log sequence number 7902924217856
InnoDB: Doing recovery: scanned up to log sequence number 7902929460736
InnoDB: Doing recovery: scanned up to log sequence number 7902934703616
InnoDB: Doing recovery: scanned up to log sequence number 7902939946496
InnoDB: Doing recovery: scanned up to log sequence number 7902945189376
InnoDB: Doing recovery: scanned up to log sequence number 7902950432256
InnoDB: Doing recovery: scanned up to log sequence number 7902955675136
InnoDB: Doing recovery: scanned up to log sequence number 7902960918016
InnoDB: Doing recovery: scanned up to log sequence number 7902966160896
InnoDB: Doing recovery: scanned up to log sequence number 7902971403776
InnoDB: Doing recovery: scanned up to log sequence number 7902976646656
InnoDB: Doing recovery: scanned up to log sequence number 7902981889536
InnoDB: Doing recovery: scanned up to log sequence number 7902987132416
InnoDB: Doing recovery: scanned up to log sequence number 7902992375296
InnoDB: Doing recovery: scanned up to log sequence number 7902997618176
InnoDB: Doing recovery: scanned up to log sequence number 7903002861056
InnoDB: Doing recovery: scanned up to log sequence number 7903008103936
InnoDB: Doing recovery: scanned up to log sequence number 7903013346816
InnoDB: Doing recovery: scanned up to log sequence number 7903018589696
InnoDB: Doing recovery: scanned up to log sequence number 7903023832576
InnoDB: Doing recovery: scanned up to log sequence number 7903029075456
InnoDB: Doing recovery: scanned up to log sequence number 7903034318336
InnoDB: Doing recovery: scanned up to log sequence number 7903039561216
InnoDB: Doing recovery: scanned up to log sequence number 7903044804096
InnoDB: Doing recovery: scanned up to log sequence number 7903050046976
InnoDB: Doing recovery: scanned up to log sequence number 7903055289856
InnoDB: Doing recovery: scanned up to log sequence number 7903060532736
InnoDB: Doing recovery: scanned up to log sequence number 7903065775616
InnoDB: Doing recovery: scanned up to log sequence number 7903071018496
InnoDB: Doing recovery: scanned up to log sequence number 7903076261376
InnoDB: Doing recovery: scanned up to log sequence number 7903081504256
InnoDB: Doing recovery: scanned up to log sequence number 7903086747136
InnoDB: Doing recovery: scanned up to log sequence number 7903091990016
InnoDB: Doing recovery: scanned up to log sequence number 7903097232896
InnoDB: Doing recovery: scanned up to log sequence number 7903102475776
InnoDB: Doing recovery: scanned up to log sequence number 7903107718656
InnoDB: Doing recovery: scanned up to log sequence number 7903112961536
InnoDB: Doing recovery: scanned up to log sequence number 7903118204416
InnoDB: Doing recovery: scanned up to log sequence number 7903123447296
InnoDB: Doing recovery: scanned up to log sequence number 7903128690176
InnoDB: Doing recovery: scanned up to log sequence number 7903133933056
InnoDB: Doing recovery: scanned up to log sequence number 7903139175936
InnoDB: Doing recovery: scanned up to log sequence number 7903144418816
InnoDB: Doing recovery: scanned up to log sequence number 7903149661696
InnoDB: Doing recovery: scanned up to log sequence number 7903154904576
InnoDB: Doing recovery: scanned up to log sequence number 7903160147456
InnoDB: Doing recovery: scanned up to log sequence number 7903165390336
InnoDB: Doing recovery: scanned up to log sequence number 7903170633216
InnoDB: Doing recovery: scanned up to log sequence number 7903175876096
InnoDB: Doing recovery: scanned up to log sequence number 7903181118976
InnoDB: Doing recovery: scanned up to log sequence number 7903186361856
InnoDB: Doing recovery: scanned up to log sequence number 7903191604736
InnoDB: Doing recovery: scanned up to log sequence number 7903196847616
InnoDB: Doing recovery: scanned up to log sequence number 7903202090496
InnoDB: Doing recovery: scanned up to log sequence number 7903207333376
InnoDB: Doing recovery: scanned up to log sequence number 7903212576256
InnoDB: Doing recovery: scanned up to log sequence number 7903217819136
InnoDB: Doing recovery: scanned up to log sequence number 7903223062016
InnoDB: Doing recovery: scanned up to log sequence number 7903228304896
InnoDB: Doing recovery: scanned up to log sequence number 7903233547776
InnoDB: Doing recovery: scanned up to log sequence number 7903238790656
InnoDB: Doing recovery: scanned up to log sequence number 7903244033536
InnoDB: Doing recovery: scanned up to log sequence number 7903249276416
InnoDB: Doing recovery: scanned up to log sequence number 7903254519296
InnoDB: Doing recovery: scanned up to log sequence number 7903259762176
InnoDB: Doing recovery: scanned up to log sequence number 7903265005056
InnoDB: Doing recovery: scanned up to log sequence number 7903270247936
InnoDB: Doing recovery: scanned up to log sequence number 7903275490816
InnoDB: Doing recovery: scanned up to log sequence number 7903280733696
InnoDB: Doing recovery: scanned up to log sequence number 7903285976576
InnoDB: Doing recovery: scanned up to log sequence number 7903291219456
InnoDB: Doing recovery: scanned up to log sequence number 7903296462336
InnoDB: Doing recovery: scanned up to log sequence number 7903301705216
InnoDB: Doing recovery: scanned up to log sequence number 7903306948096
InnoDB: Doing recovery: scanned up to log sequence number 7903312190976
InnoDB: Doing recovery: scanned up to log sequence number 7903317433856
InnoDB: Doing recovery: scanned up to log sequence number 7903322676736
InnoDB: Doing recovery: scanned up to log sequence number 7903327919616
InnoDB: Doing recovery: scanned up to log sequence number 7903333162496
InnoDB: Doing recovery: scanned up to log sequence number 7903338405376
InnoDB: Doing recovery: scanned up to log sequence number 7903343648256
InnoDB: Doing recovery: scanned up to log sequence number 7903348891136
InnoDB: Doing recovery: scanned up to log sequence number 7903354134016
InnoDB: Doing recovery: scanned up to log sequence number 7903359376896
InnoDB: Doing recovery: scanned up to log sequence number 7903364619776
InnoDB: Doing recovery: scanned up to log sequence number 7903369862656
InnoDB: Doing recovery: scanned up to log sequence number 7903375105536
InnoDB: Doing recovery: scanned up to log sequence number 7903380348416
InnoDB: Doing recovery: scanned up to log sequence number 7903385591296
InnoDB: Doing recovery: scanned up to log sequence number 7903390834176
InnoDB: Doing recovery: scanned up to log sequence number 7903396077056
InnoDB: Doing recovery: scanned up to log sequence number 7903401319936
InnoDB: Doing recovery: scanned up to log sequence number 7903406562816
InnoDB: Doing recovery: scanned up to log sequence number 7903411805696
InnoDB: Doing recovery: scanned up to log sequence number 7903417048576
InnoDB: Doing recovery: scanned up to log sequence number 7903422291456
InnoDB: Doing recovery: scanned up to log sequence number 7903427534336
InnoDB: Doing recovery: scanned up to log sequence number 7903432777216
InnoDB: Doing recovery: scanned up to log sequence number 7903438020096
InnoDB: Doing recovery: scanned up to log sequence number 7903443262976
InnoDB: Doing recovery: scanned up to log sequence number 7903448505856
InnoDB: Doing recovery: scanned up to log sequence number 7903453748736
InnoDB: Doing recovery: scanned up to log sequence number 7903458991616
InnoDB: Doing recovery: scanned up to log sequence number 7903464234496
InnoDB: Doing recovery: scanned up to log sequence number 7903469477376
InnoDB: Doing recovery: scanned up to log sequence number 7903474720256
InnoDB: Doing recovery: scanned up to log sequence number 7903479963136
InnoDB: Doing recovery: scanned up to log sequence number 7903485206016
InnoDB: Doing recovery: scanned up to log sequence number 7903490448896
InnoDB: Doing recovery: scanned up to log sequence number 7903495691776
InnoDB: Doing recovery: scanned up to log sequence number 7903500934656
InnoDB: Doing recovery: scanned up to log sequence number 7903506177536
InnoDB: Doing recovery: scanned up to log sequence number 7903511420416
InnoDB: Doing recovery: scanned up to log sequence number 7903516663296
InnoDB: Doing recovery: scanned up to log sequence number 7903521906176
InnoDB: Doing recovery: scanned up to log sequence number 7903527149056
InnoDB: Doing recovery: scanned up to log sequence number 7903532391936
InnoDB: Doing recovery: scanned up to log sequence number 7903537634816
InnoDB: Doing recovery: scanned up to log sequence number 7903542877696
InnoDB: Doing recovery: scanned up to log sequence number 7903548120576
InnoDB: Doing recovery: scanned up to log sequence number 7903553363456
InnoDB: Doing recovery: scanned up to log sequence number 7903558606336
InnoDB: Doing recovery: scanned up to log sequence number 7903563849216
InnoDB: Doing recovery: scanned up to log sequence number 7903569092096
InnoDB: Doing recovery: scanned up to log sequence number 7903574334976
InnoDB: Doing recovery: scanned up to log sequence number 7903579577856
InnoDB: Doing recovery: scanned up to log sequence number 7903584820736
InnoDB: Doing recovery: scanned up to log sequence number 7903590063616
InnoDB: Doing recovery: scanned up to log sequence number 7903595306496
InnoDB: Doing recovery: scanned up to log sequence number 7903600549376
InnoDB: Doing recovery: scanned up to log sequence number 7903605792256
InnoDB: Doing recovery: scanned up to log sequence number 7903611035136
InnoDB: Doing recovery: scanned up to log sequence number 7903616278016
InnoDB: Doing recovery: scanned up to log sequence number 7903621520896
InnoDB: Doing recovery: scanned up to log sequence number 7903626763776
InnoDB: Doing recovery: scanned up to log sequence number 7903632006656
InnoDB: Doing recovery: scanned up to log sequence number 7903637249536
InnoDB: Doing recovery: scanned up to log sequence number 7903642492416
InnoDB: Doing recovery: scanned up to log sequence number 7903647735296
InnoDB: Doing recovery: scanned up to log sequence number 7903652978176
InnoDB: Doing recovery: scanned up to log sequence number 7903658221056
InnoDB: Doing recovery: scanned up to log sequence number 7903663463936
InnoDB: Doing recovery: scanned up to log sequence number 7903668706816
InnoDB: Doing recovery: scanned up to log sequence number 7903673949696
InnoDB: Doing recovery: scanned up to log sequence number 7903679192576
InnoDB: Doing recovery: scanned up to log sequence number 7903684435456
InnoDB: Doing recovery: scanned up to log sequence number 7903689678336
InnoDB: Doing recovery: scanned up to log sequence number 7903694921216
InnoDB: Doing recovery: scanned up to log sequence number 7903700164096
InnoDB: Doing recovery: scanned up to log sequence number 7903705406976
InnoDB: Doing recovery: scanned up to log sequence number 7903710649856
InnoDB: Doing recovery: scanned up to log sequence number 7903715892736
InnoDB: Doing recovery: scanned up to log sequence number 7903721135616
InnoDB: Doing recovery: scanned up to log sequence number 7903726378496
InnoDB: Doing recovery: scanned up to log sequence number 7903731621376
InnoDB: Doing recovery: scanned up to log sequence number 7903736864256
InnoDB: Doing recovery: scanned up to log sequence number 7903742107136
InnoDB: Doing recovery: scanned up to log sequence number 7903747350016
InnoDB: Doing recovery: scanned up to log sequence number 7903752592896
InnoDB: Doing recovery: scanned up to log sequence number 7903757835776
InnoDB: Doing recovery: scanned up to log sequence number 7903763078656
InnoDB: Doing recovery: scanned up to log sequence number 7903768321536
InnoDB: Doing recovery: scanned up to log sequence number 7903773564416
InnoDB: Doing recovery: scanned up to log sequence number 7903778807296
InnoDB: Doing recovery: scanned up to log sequence number 7903784050176
InnoDB: Doing recovery: scanned up to log sequence number 7903789293056
InnoDB: Doing recovery: scanned up to log sequence number 7903794535936
InnoDB: Doing recovery: scanned up to log sequence number 7903799778816
InnoDB: Doing recovery: scanned up to log sequence number 7903805021696
InnoDB: Doing recovery: scanned up to log sequence number 7903810264576
InnoDB: Doing recovery: scanned up to log sequence number 7903815507456
InnoDB: Doing recovery: scanned up to log sequence number 7903820750336
InnoDB: Doing recovery: scanned up to log sequence number 7903825993216
InnoDB: Doing recovery: scanned up to log sequence number 7903831236096
InnoDB: Doing recovery: scanned up to log sequence number 7903836478976
InnoDB: Doing recovery: scanned up to log sequence number 7903841721856
InnoDB: Doing recovery: scanned up to log sequence number 7903846964736
InnoDB: Doing recovery: scanned up to log sequence number 7903852207616
InnoDB: Doing recovery: scanned up to log sequence number 7903857450496
InnoDB: Doing recovery: scanned up to log sequence number 7903862693376
InnoDB: Doing recovery: scanned up to log sequence number 7903867936256
InnoDB: Doing recovery: scanned up to log sequence number 7903873179136
InnoDB: Doing recovery: scanned up to log sequence number 7903878422016
InnoDB: Doing recovery: scanned up to log sequence number 7903883664896
InnoDB: Doing recovery: scanned up to log sequence number 7903888907776
InnoDB: Doing recovery: scanned up to log sequence number 7903894150656
InnoDB: Doing recovery: scanned up to log sequence number 7903899393536
InnoDB: Doing recovery: scanned up to log sequence number 7903904636416
InnoDB: Doing recovery: scanned up to log sequence number 7903909879296
InnoDB: Doing recovery: scanned up to log sequence number 7903915122176
InnoDB: Doing recovery: scanned up to log sequence number 7903920365056
InnoDB: Doing recovery: scanned up to log sequence number 7903925607936
InnoDB: Doing recovery: scanned up to log sequence number 7903930850816
InnoDB: Doing recovery: scanned up to log sequence number 7903936093696
InnoDB: Doing recovery: scanned up to log sequence number 7903941336576
InnoDB: Doing recovery: scanned up to log sequence number 7903946579456
InnoDB: Doing recovery: scanned up to log sequence number 7903951822336
InnoDB: Doing recovery: scanned up to log sequence number 7903957065216
InnoDB: Doing recovery: scanned up to log sequence number 7903962308096
InnoDB: Doing recovery: scanned up to log sequence number 7903967550976
InnoDB: Doing recovery: scanned up to log sequence number 7903972793856
InnoDB: Doing recovery: scanned up to log sequence number 7903978036736
InnoDB: Doing recovery: scanned up to log sequence number 7903983279616
InnoDB: Doing recovery: scanned up to log sequence number 7903988522496
InnoDB: Doing recovery: scanned up to log sequence number 7903993765376
InnoDB: Doing recovery: scanned up to log sequence number 7903999008256
InnoDB: Doing recovery: scanned up to log sequence number 7904004251136
InnoDB: Doing recovery: scanned up to log sequence number 7904009494016
InnoDB: Doing recovery: scanned up to log sequence number 7904014736896
InnoDB: Doing recovery: scanned up to log sequence number 7904019979776
InnoDB: Doing recovery: scanned up to log sequence number 7904025222656
InnoDB: Doing recovery: scanned up to log sequence number 7904030465536
InnoDB: Doing recovery: scanned up to log sequence number 7904035708416
InnoDB: Doing recovery: scanned up to log sequence number 7904040951296
InnoDB: Doing recovery: scanned up to log sequence number 7904046194176
InnoDB: Doing recovery: scanned up to log sequence number 7904051437056
InnoDB: Doing recovery: scanned up to log sequence number 7904056679936
InnoDB: Doing recovery: scanned up to log sequence number 7904061922816
InnoDB: Doing recovery: scanned up to log sequence number 7904067165696
InnoDB: Doing recovery: scanned up to log sequence number 7904072408576
InnoDB: Doing recovery: scanned up to log sequence number 7904077651456
InnoDB: Doing recovery: scanned up to log sequence number 7904082894336
InnoDB: Doing recovery: scanned up to log sequence number 7904088137216
InnoDB: Doing recovery: scanned up to log sequence number 7904093380096
InnoDB: Doing recovery: scanned up to log sequence number 7904098622976
InnoDB: Doing recovery: scanned up to log sequence number 7904103865856
InnoDB: Doing recovery: scanned up to log sequence number 7904109108736
InnoDB: Doing recovery: scanned up to log sequence number 7904114351616
InnoDB: Doing recovery: scanned up to log sequence number 7904119594496
InnoDB: Doing recovery: scanned up to log sequence number 7904124837376
InnoDB: Doing recovery: scanned up to log sequence number 7904130080256
InnoDB: Doing recovery: scanned up to log sequence number 7904135323136
InnoDB: Doing recovery: scanned up to log sequence number 7904140566016
InnoDB: Doing recovery: scanned up to log sequence number 7904145808896
InnoDB: Doing recovery: scanned up to log sequence number 7904151051776
InnoDB: Doing recovery: scanned up to log sequence number 7904156294656
InnoDB: Doing recovery: scanned up to log sequence number 7904161537536
InnoDB: Doing recovery: scanned up to log sequence number 7904166780416
InnoDB: Doing recovery: scanned up to log sequence number 7904172023296
InnoDB: Doing recovery: scanned up to log sequence number 7904177266176
InnoDB: Doing recovery: scanned up to log sequence number 7904182509056
InnoDB: Doing recovery: scanned up to log sequence number 7904187751936
InnoDB: Doing recovery: scanned up to log sequence number 7904192994816
InnoDB: Doing recovery: scanned up to log sequence number 7904198237696
InnoDB: Doing recovery: scanned up to log sequence number 7904203480576
InnoDB: Doing recovery: scanned up to log sequence number 7904208723456
InnoDB: Doing recovery: scanned up to log sequence number 7904213966336
InnoDB: Doing recovery: scanned up to log sequence number 7904219209216
InnoDB: Doing recovery: scanned up to log sequence number 7904224452096
InnoDB: Doing recovery: scanned up to log sequence number 7904229694976
InnoDB: Doing recovery: scanned up to log sequence number 7904234937856
InnoDB: Doing recovery: scanned up to log sequence number 7904240180736
InnoDB: Doing recovery: scanned up to log sequence number 7904245423616
InnoDB: Doing recovery: scanned up to log sequence number 7904250666496
InnoDB: Doing recovery: scanned up to log sequence number 7904255909376
InnoDB: Doing recovery: scanned up to log sequence number 7904261152256
InnoDB: Doing recovery: scanned up to log sequence number 7904266395136
InnoDB: Doing recovery: scanned up to log sequence number 7904271638016
InnoDB: Doing recovery: scanned up to log sequence number 7904276880896
InnoDB: Doing recovery: scanned up to log sequence number 7904282123776
InnoDB: Doing recovery: scanned up to log sequence number 7904287366656
InnoDB: Doing recovery: scanned up to log sequence number 7904292609536
InnoDB: Doing recovery: scanned up to log sequence number 7904297852416
InnoDB: Doing recovery: scanned up to log sequence number 7904303095296
InnoDB: Doing recovery: scanned up to log sequence number 7904308338176
InnoDB: Doing recovery: scanned up to log sequence number 7904313581056
InnoDB: Doing recovery: scanned up to log sequence number 7904318823936
InnoDB: Doing recovery: scanned up to log sequence number 7904324066816
InnoDB: Doing recovery: scanned up to log sequence number 7904329309696
InnoDB: Doing recovery: scanned up to log sequence number 7904334552576
InnoDB: Doing recovery: scanned up to log sequence number 7904339795456
InnoDB: Doing recovery: scanned up to log sequence number 7904345038336
InnoDB: Doing recovery: scanned up to log sequence number 7904350281216
InnoDB: Doing recovery: scanned up to log sequence number 7904355524096
InnoDB: Doing recovery: scanned up to log sequence number 7904360766976
InnoDB: Doing recovery: scanned up to log sequence number 7904366009856
InnoDB: Doing recovery: scanned up to log sequence number 7904371252736
InnoDB: Doing recovery: scanned up to log sequence number 7904376495616
InnoDB: Doing recovery: scanned up to log sequence number 7904381738496
InnoDB: Doing recovery: scanned up to log sequence number 7904386981376
InnoDB: Doing recovery: scanned up to log sequence number 7904392224256
InnoDB: Doing recovery: scanned up to log sequence number 7904397467136
InnoDB: Doing recovery: scanned up to log sequence number 7904402710016
InnoDB: Doing recovery: scanned up to log sequence number 7904407952896
InnoDB: Doing recovery: scanned up to log sequence number 7904413195776
InnoDB: Doing recovery: scanned up to log sequence number 7904418438656
InnoDB: Doing recovery: scanned up to log sequence number 7904423681536
InnoDB: Doing recovery: scanned up to log sequence number 7904428924416
InnoDB: Doing recovery: scanned up to log sequence number 7904434167296
InnoDB: Doing recovery: scanned up to log sequence number 7904439410176
InnoDB: Doing recovery: scanned up to log sequence number 7904444653056
InnoDB: Doing recovery: scanned up to log sequence number 7904449895936
InnoDB: Doing recovery: scanned up to log sequence number 7904455138816
InnoDB: Doing recovery: scanned up to log sequence number 7904460381696
InnoDB: Doing recovery: scanned up to log sequence number 7904465624576
InnoDB: Doing recovery: scanned up to log sequence number 7904470867456
InnoDB: Doing recovery: scanned up to log sequence number 7904476110336
InnoDB: Doing recovery: scanned up to log sequence number 7904481353216
InnoDB: Doing recovery: scanned up to log sequence number 7904486596096
InnoDB: Doing recovery: scanned up to log sequence number 7904491838976
InnoDB: Doing recovery: scanned up to log sequence number 7904497081856
InnoDB: Doing recovery: scanned up to log sequence number 7904502324736
InnoDB: Doing recovery: scanned up to log sequence number 7904507567616
InnoDB: Doing recovery: scanned up to log sequence number 7904512810496
InnoDB: Doing recovery: scanned up to log sequence number 7904518053376
InnoDB: Doing recovery: scanned up to log sequence number 7904523296256
InnoDB: Doing recovery: scanned up to log sequence number 7904528539136
InnoDB: Doing recovery: scanned up to log sequence number 7904533782016
InnoDB: Doing recovery: scanned up to log sequence number 7904539024896
InnoDB: Doing recovery: scanned up to log sequence number 7904544267776
InnoDB: Doing recovery: scanned up to log sequence number 7904549510656
InnoDB: Doing recovery: scanned up to log sequence number 7904554753536
InnoDB: Doing recovery: scanned up to log sequence number 7904559996416
InnoDB: Doing recovery: scanned up to log sequence number 7904565239296
InnoDB: Doing recovery: scanned up to log sequence number 7904570482176
InnoDB: Doing recovery: scanned up to log sequence number 7904575725056
InnoDB: Doing recovery: scanned up to log sequence number 7904580967936
InnoDB: Doing recovery: scanned up to log sequence number 7904586210816
InnoDB: Doing recovery: scanned up to log sequence number 7904591453696
InnoDB: Doing recovery: scanned up to log sequence number 7904596696576
InnoDB: Doing recovery: scanned up to log sequence number 7904601939456
InnoDB: Doing recovery: scanned up to log sequence number 7904607182336
InnoDB: Doing recovery: scanned up to log sequence number 7904612425216
InnoDB: Doing recovery: scanned up to log sequence number 7904617668096
InnoDB: Doing recovery: scanned up to log sequence number 7904622910976
InnoDB: Doing recovery: scanned up to log sequence number 7904628153856
InnoDB: Doing recovery: scanned up to log sequence number 7904633396736
InnoDB: Doing recovery: scanned up to log sequence number 7904638639616
InnoDB: Doing recovery: scanned up to log sequence number 7904643882496
InnoDB: Doing recovery: scanned up to log sequence number 7904649125376
InnoDB: Doing recovery: scanned up to log sequence number 7904654368256
InnoDB: Doing recovery: scanned up to log sequence number 7904659611136
InnoDB: Doing recovery: scanned up to log sequence number 7904664854016
InnoDB: Doing recovery: scanned up to log sequence number 7904670096896
InnoDB: Doing recovery: scanned up to log sequence number 7904675339776
InnoDB: Doing recovery: scanned up to log sequence number 7904680582656
InnoDB: Doing recovery: scanned up to log sequence number 7904685825536
InnoDB: Doing recovery: scanned up to log sequence number 7904691068416
InnoDB: Doing recovery: scanned up to log sequence number 7904696311296
InnoDB: Doing recovery: scanned up to log sequence number 7904701554176
InnoDB: Doing recovery: scanned up to log sequence number 7904706797056
InnoDB: Doing recovery: scanned up to log sequence number 7904712039936
InnoDB: Doing recovery: scanned up to log sequence number 7904717282816
InnoDB: Doing recovery: scanned up to log sequence number 7904722525696
InnoDB: Doing recovery: scanned up to log sequence number 7904727768576
InnoDB: Doing recovery: scanned up to log sequence number 7904733011456
InnoDB: Doing recovery: scanned up to log sequence number 7904738254336
InnoDB: Doing recovery: scanned up to log sequence number 7904743497216
InnoDB: Doing recovery: scanned up to log sequence number 7904748740096
InnoDB: Doing recovery: scanned up to log sequence number 7904753982976
InnoDB: Doing recovery: scanned up to log sequence number 7904759225856
InnoDB: Doing recovery: scanned up to log sequence number 7904764468736
InnoDB: Doing recovery: scanned up to log sequence number 7904769711616
InnoDB: Doing recovery: scanned up to log sequence number 7904774954496
InnoDB: Doing recovery: scanned up to log sequence number 7904780197376
InnoDB: Doing recovery: scanned up to log sequence number 7904785440256
InnoDB: Doing recovery: scanned up to log sequence number 7904790683136
InnoDB: Doing recovery: scanned up to log sequence number 7904795926016
InnoDB: Doing recovery: scanned up to log sequence number 7904801168896
InnoDB: Doing recovery: scanned up to log sequence number 7904806411776
InnoDB: Doing recovery: scanned up to log sequence number 7904811654656
InnoDB: Doing recovery: scanned up to log sequence number 7904816897536
InnoDB: Doing recovery: scanned up to log sequence number 7904822140416
InnoDB: Doing recovery: scanned up to log sequence number 7904827383296
InnoDB: Doing recovery: scanned up to log sequence number 7904832626176
InnoDB: Doing recovery: scanned up to log sequence number 7904837869056
InnoDB: Doing recovery: scanned up to log sequence number 7904843111936
InnoDB: Doing recovery: scanned up to log sequence number 7904848354816
InnoDB: Doing recovery: scanned up to log sequence number 7904853597696
InnoDB: Doing recovery: scanned up to log sequence number 7904858840576
InnoDB: Doing recovery: scanned up to log sequence number 7904864083456
InnoDB: Doing recovery: scanned up to log sequence number 7904869326336
InnoDB: Doing recovery: scanned up to log sequence number 7904874569216
InnoDB: Doing recovery: scanned up to log sequence number 7904879812096
InnoDB: Doing recovery: scanned up to log sequence number 7904885054976
InnoDB: Doing recovery: scanned up to log sequence number 7904890297856
InnoDB: Doing recovery: scanned up to log sequence number 7904895540736
InnoDB: Doing recovery: scanned up to log sequence number 7904900783616
InnoDB: Doing recovery: scanned up to log sequence number 7904906026496
InnoDB: Doing recovery: scanned up to log sequence number 7904911269376
InnoDB: Doing recovery: scanned up to log sequence number 7904916512256
InnoDB: Doing recovery: scanned up to log sequence number 7904921755136
InnoDB: Doing recovery: scanned up to log sequence number 7904926998016
InnoDB: Doing recovery: scanned up to log sequence number 7904932240896
InnoDB: Doing recovery: scanned up to log sequence number 7904937483776
InnoDB: Doing recovery: scanned up to log sequence number 7904942726656
InnoDB: Doing recovery: scanned up to log sequence number 7904947969536
InnoDB: Doing recovery: scanned up to log sequence number 7904953212416
InnoDB: Doing recovery: scanned up to log sequence number 7904958455296
InnoDB: Doing recovery: scanned up to log sequence number 7904963698176
InnoDB: Doing recovery: scanned up to log sequence number 7904968941056
InnoDB: Doing recovery: scanned up to log sequence number 7904974183936
InnoDB: Doing recovery: scanned up to log sequence number 7904979426816
InnoDB: Doing recovery: scanned up to log sequence number 7904984669696
InnoDB: Doing recovery: scanned up to log sequence number 7904989912576
InnoDB: Doing recovery: scanned up to log sequence number 7904995155456
InnoDB: Doing recovery: scanned up to log sequence number 7905000398336
InnoDB: Doing recovery: scanned up to log sequence number 7905005641216
InnoDB: Doing recovery: scanned up to log sequence number 7905010884096
InnoDB: Doing recovery: scanned up to log sequence number 7905016126976
InnoDB: Doing recovery: scanned up to log sequence number 7905021369856
InnoDB: Doing recovery: scanned up to log sequence number 7905026612736
InnoDB: Doing recovery: scanned up to log sequence number 7905031855616
InnoDB: Doing recovery: scanned up to log sequence number 7905037098496
InnoDB: Doing recovery: scanned up to log sequence number 7905042341376
InnoDB: Doing recovery: scanned up to log sequence number 7905047584256
InnoDB: Doing recovery: scanned up to log sequence number 7905052827136
InnoDB: Doing recovery: scanned up to log sequence number 7905058070016
InnoDB: Doing recovery: scanned up to log sequence number 7905063312896
InnoDB: Doing recovery: scanned up to log sequence number 7905068555776
InnoDB: Doing recovery: scanned up to log sequence number 7905073798656
InnoDB: Doing recovery: scanned up to log sequence number 7905079041536
InnoDB: Doing recovery: scanned up to log sequence number 7905084284416
InnoDB: Doing recovery: scanned up to log sequence number 7905089527296
InnoDB: Doing recovery: scanned up to log sequence number 7905094770176
InnoDB: Doing recovery: scanned up to log sequence number 7905100013056
InnoDB: Doing recovery: scanned up to log sequence number 7905105255936
InnoDB: Doing recovery: scanned up to log sequence number 7905110498816
InnoDB: Doing recovery: scanned up to log sequence number 7905115741696
InnoDB: Doing recovery: scanned up to log sequence number 7905120984576
InnoDB: Doing recovery: scanned up to log sequence number 7905126227456
InnoDB: Doing recovery: scanned up to log sequence number 7905131470336
InnoDB: Doing recovery: scanned up to log sequence number 7905136713216
InnoDB: Doing recovery: scanned up to log sequence number 7905141956096
InnoDB: Doing recovery: scanned up to log sequence number 7905147198976
InnoDB: Doing recovery: scanned up to log sequence number 7905152441856
InnoDB: Doing recovery: scanned up to log sequence number 7905157684736
InnoDB: Doing recovery: scanned up to log sequence number 7905162927616
InnoDB: Doing recovery: scanned up to log sequence number 7905168170496
InnoDB: Doing recovery: scanned up to log sequence number 7905173413376
InnoDB: Doing recovery: scanned up to log sequence number 7905178656256
InnoDB: Doing recovery: scanned up to log sequence number 7905183899136
InnoDB: Doing recovery: scanned up to log sequence number 7905189142016
InnoDB: Doing recovery: scanned up to log sequence number 7905194384896
InnoDB: Doing recovery: scanned up to log sequence number 7905199627776
InnoDB: Doing recovery: scanned up to log sequence number 7905204870656
InnoDB: Doing recovery: scanned up to log sequence number 7905210113536
InnoDB: Doing recovery: scanned up to log sequence number 7905215356416
InnoDB: Doing recovery: scanned up to log sequence number 7905220599296
InnoDB: Doing recovery: scanned up to log sequence number 7905225842176
InnoDB: Doing recovery: scanned up to log sequence number 7905231085056
InnoDB: Doing recovery: scanned up to log sequence number 7905236327936
InnoDB: Doing recovery: scanned up to log sequence number 7905241570816
InnoDB: Doing recovery: scanned up to log sequence number 7905246813696
InnoDB: Doing recovery: scanned up to log sequence number 7905252056576
InnoDB: Doing recovery: scanned up to log sequence number 7905257299456
InnoDB: Doing recovery: scanned up to log sequence number 7905262542336
InnoDB: Doing recovery: scanned up to log sequence number 7905267785216
InnoDB: Doing recovery: scanned up to log sequence number 7905273028096
InnoDB: Doing recovery: scanned up to log sequence number 7905278270976
InnoDB: Doing recovery: scanned up to log sequence number 7905283513856
InnoDB: Doing recovery: scanned up to log sequence number 7905288756736
InnoDB: Doing recovery: scanned up to log sequence number 7905293999616
InnoDB: Doing recovery: scanned up to log sequence number 7905299242496
InnoDB: Doing recovery: scanned up to log sequence number 7905304485376
InnoDB: Doing recovery: scanned up to log sequence number 7905309728256
InnoDB: Doing recovery: scanned up to log sequence number 7905314971136
InnoDB: Doing recovery: scanned up to log sequence number 7905320214016
InnoDB: Doing recovery: scanned up to log sequence number 7905325456896
InnoDB: Doing recovery: scanned up to log sequence number 7905330699776
InnoDB: Doing recovery: scanned up to log sequence number 7905335942656
InnoDB: Doing recovery: scanned up to log sequence number 7905341185536
InnoDB: Doing recovery: scanned up to log sequence number 7905346428416
InnoDB: Doing recovery: scanned up to log sequence number 7905351671296
InnoDB: Doing recovery: scanned up to log sequence number 7905356914176
InnoDB: Doing recovery: scanned up to log sequence number 7905362157056
InnoDB: Doing recovery: scanned up to log sequence number 7905367399936
InnoDB: Doing recovery: scanned up to log sequence number 7905372642816
InnoDB: Doing recovery: scanned up to log sequence number 7905377885696
InnoDB: Doing recovery: scanned up to log sequence number 7905383128576
InnoDB: Doing recovery: scanned up to log sequence number 7905388371456
InnoDB: Doing recovery: scanned up to log sequence number 7905393614336
InnoDB: Doing recovery: scanned up to log sequence number 7905398857216
InnoDB: Doing recovery: scanned up to log sequence number 7905404100096
InnoDB: Doing recovery: scanned up to log sequence number 7905409342976
InnoDB: Doing recovery: scanned up to log sequence number 7905414585856
InnoDB: Doing recovery: scanned up to log sequence number 7905419828736
InnoDB: Doing recovery: scanned up to log sequence number 7905425071616
InnoDB: Doing recovery: scanned up to log sequence number 7905430314496
InnoDB: Doing recovery: scanned up to log sequence number 7905435557376
InnoDB: Doing recovery: scanned up to log sequence number 7905440800256
InnoDB: Doing recovery: scanned up to log sequence number 7905446043136
InnoDB: Doing recovery: scanned up to log sequence number 7905451286016
InnoDB: Doing recovery: scanned up to log sequence number 7905456528896
InnoDB: Doing recovery: scanned up to log sequence number 7905461771776
InnoDB: Doing recovery: scanned up to log sequence number 7905467014656
InnoDB: Doing recovery: scanned up to log sequence number 7905472257536
InnoDB: Doing recovery: scanned up to log sequence number 7905477500416
InnoDB: Doing recovery: scanned up to log sequence number 7905482743296
InnoDB: Doing recovery: scanned up to log sequence number 7905487986176
InnoDB: Doing recovery: scanned up to log sequence number 7905493229056
InnoDB: Doing recovery: scanned up to log sequence number 7905498471936
InnoDB: Doing recovery: scanned up to log sequence number 7905503714816
InnoDB: Doing recovery: scanned up to log sequence number 7905508957696
InnoDB: Doing recovery: scanned up to log sequence number 7905514200576
InnoDB: Doing recovery: scanned up to log sequence number 7905519443456
InnoDB: Doing recovery: scanned up to log sequence number 7905524686336
InnoDB: Doing recovery: scanned up to log sequence number 7905529929216
InnoDB: Doing recovery: scanned up to log sequence number 7905535172096
InnoDB: Doing recovery: scanned up to log sequence number 7905540414976
InnoDB: Doing recovery: scanned up to log sequence number 7905545657856
InnoDB: Doing recovery: scanned up to log sequence number 7905550900736
InnoDB: Doing recovery: scanned up to log sequence number 7905556143616
InnoDB: Doing recovery: scanned up to log sequence number 7905561386496
InnoDB: Doing recovery: scanned up to log sequence number 7905566629376
InnoDB: Doing recovery: scanned up to log sequence number 7905571872256
InnoDB: Doing recovery: scanned up to log sequence number 7905577115136
InnoDB: Doing recovery: scanned up to log sequence number 7905582358016
InnoDB: Doing recovery: scanned up to log sequence number 7905587600896
InnoDB: Doing recovery: scanned up to log sequence number 7905592843776
InnoDB: Doing recovery: scanned up to log sequence number 7905598086656
InnoDB: Doing recovery: scanned up to log sequence number 7905603329536
InnoDB: Doing recovery: scanned up to log sequence number 7905608572416
InnoDB: Doing recovery: scanned up to log sequence number 7905613815296
InnoDB: Doing recovery: scanned up to log sequence number 7905619058176
InnoDB: Doing recovery: scanned up to log sequence number 7905624301056
InnoDB: Doing recovery: scanned up to log sequence number 7905629543936
InnoDB: Doing recovery: scanned up to log sequence number 7905634786816
InnoDB: Doing recovery: scanned up to log sequence number 7905640029696
InnoDB: Doing recovery: scanned up to log sequence number 7905645272576
InnoDB: Doing recovery: scanned up to log sequence number 7905650515456
InnoDB: Doing recovery: scanned up to log sequence number 7905655758336
InnoDB: Doing recovery: scanned up to log sequence number 7905661001216
InnoDB: Doing recovery: scanned up to log sequence number 7905666244096
InnoDB: Doing recovery: scanned up to log sequence number 7905671486976
InnoDB: Doing recovery: scanned up to log sequence number 7905676729856
InnoDB: Doing recovery: scanned up to log sequence number 7905681972736
InnoDB: Doing recovery: scanned up to log sequence number 7905687215616
InnoDB: Doing recovery: scanned up to log sequence number 7905692458496
InnoDB: Doing recovery: scanned up to log sequence number 7905697701376
InnoDB: Doing recovery: scanned up to log sequence number 7905702944256
InnoDB: Doing recovery: scanned up to log sequence number 7905708187136
InnoDB: Doing recovery: scanned up to log sequence number 7905713430016
InnoDB: Doing recovery: scanned up to log sequence number 7905718672896
InnoDB: Doing recovery: scanned up to log sequence number 7905723915776
InnoDB: Doing recovery: scanned up to log sequence number 7905729158656
InnoDB: Doing recovery: scanned up to log sequence number 7905734401536
InnoDB: Doing recovery: scanned up to log sequence number 7905739644416
InnoDB: Doing recovery: scanned up to log sequence number 7905744887296
InnoDB: Doing recovery: scanned up to log sequence number 7905750130176
InnoDB: Doing recovery: scanned up to log sequence number 7905755373056
InnoDB: Doing recovery: scanned up to log sequence number 7905760615936
InnoDB: Doing recovery: scanned up to log sequence number 7905765858816
InnoDB: Doing recovery: scanned up to log sequence number 7905771101696
InnoDB: Doing recovery: scanned up to log sequence number 7905776344576
InnoDB: Doing recovery: scanned up to log sequence number 7905781587456
InnoDB: Doing recovery: scanned up to log sequence number 7905786830336
InnoDB: Doing recovery: scanned up to log sequence number 7905792073216
InnoDB: Doing recovery: scanned up to log sequence number 7905797316096
InnoDB: Doing recovery: scanned up to log sequence number 7905802558976
InnoDB: Doing recovery: scanned up to log sequence number 7905807801856
InnoDB: Doing recovery: scanned up to log sequence number 7905813044736
InnoDB: Doing recovery: scanned up to log sequence number 7905818287616
InnoDB: Doing recovery: scanned up to log sequence number 7905823530496
InnoDB: Doing recovery: scanned up to log sequence number 7905828773376
InnoDB: Doing recovery: scanned up to log sequence number 7905834016256
InnoDB: Doing recovery: scanned up to log sequence number 7905839259136
InnoDB: Doing recovery: scanned up to log sequence number 7905844502016
InnoDB: Doing recovery: scanned up to log sequence number 7905849744896
InnoDB: Doing recovery: scanned up to log sequence number 7905854987776
InnoDB: Doing recovery: scanned up to log sequence number 7905860230656
InnoDB: Doing recovery: scanned up to log sequence number 7905865473536
InnoDB: Doing recovery: scanned up to log sequence number 7905870716416
InnoDB: Doing recovery: scanned up to log sequence number 7905875959296
InnoDB: Doing recovery: scanned up to log sequence number 7905881202176
InnoDB: Doing recovery: scanned up to log sequence number 7905886445056
InnoDB: Doing recovery: scanned up to log sequence number 7905891687936
InnoDB: Doing recovery: scanned up to log sequence number 7905896930816
InnoDB: Doing recovery: scanned up to log sequence number 7905902173696
InnoDB: Doing recovery: scanned up to log sequence number 7905907416576
InnoDB: Doing recovery: scanned up to log sequence number 7905912659456
InnoDB: Doing recovery: scanned up to log sequence number 7905917902336
InnoDB: Doing recovery: scanned up to log sequence number 7905923145216
InnoDB: Doing recovery: scanned up to log sequence number 7905928388096
InnoDB: Doing recovery: scanned up to log sequence number 7905933630976
InnoDB: Doing recovery: scanned up to log sequence number 7905938873856
InnoDB: Doing recovery: scanned up to log sequence number 7905944116736
InnoDB: Doing recovery: scanned up to log sequence number 7905949359616
InnoDB: Doing recovery: scanned up to log sequence number 7905954602496
InnoDB: Doing recovery: scanned up to log sequence number 7905959845376
InnoDB: Doing recovery: scanned up to log sequence number 7905965088256
InnoDB: Doing recovery: scanned up to log sequence number 7905970331136
InnoDB: Doing recovery: scanned up to log sequence number 7905975574016
InnoDB: Doing recovery: scanned up to log sequence number 7905980816896
InnoDB: Doing recovery: scanned up to log sequence number 7905986059776
InnoDB: Doing recovery: scanned up to log sequence number 7905991302656
InnoDB: Doing recovery: scanned up to log sequence number 7905996545536
InnoDB: Doing recovery: scanned up to log sequence number 7906001788416
InnoDB: Doing recovery: scanned up to log sequence number 7906007031296
InnoDB: Doing recovery: scanned up to log sequence number 7906012274176
InnoDB: Doing recovery: scanned up to log sequence number 7906017517056
InnoDB: Doing recovery: scanned up to log sequence number 7906022759936
InnoDB: Doing recovery: scanned up to log sequence number 7906028002816
InnoDB: Doing recovery: scanned up to log sequence number 7906033245696
InnoDB: Doing recovery: scanned up to log sequence number 7906038488576
InnoDB: Doing recovery: scanned up to log sequence number 7906043731456
InnoDB: Doing recovery: scanned up to log sequence number 7906048974336
InnoDB: Doing recovery: scanned up to log sequence number 7906054217216
InnoDB: Doing recovery: scanned up to log sequence number 7906059460096
InnoDB: Doing recovery: scanned up to log sequence number 7906064702976
InnoDB: Doing recovery: scanned up to log sequence number 7906069945856
InnoDB: Doing recovery: scanned up to log sequence number 7906075188736
InnoDB: Doing recovery: scanned up to log sequence number 7906080431616
InnoDB: Doing recovery: scanned up to log sequence number 7906085674496
InnoDB: Doing recovery: scanned up to log sequence number 7906090917376
InnoDB: Doing recovery: scanned up to log sequence number 7906092439081
InnoDB: Transaction 12598911 was in the XA prepared state.
InnoDB: 10 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 75221 row operations to undo
InnoDB: Trx id counter is 12599296
2017-06-29 13:00:54 54072 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 1072072835, file name bin-log.001158
2017-06-29 13:06:01 54072 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2017-06-29 13:06:01 7e59c4317700 InnoDB: Rolling back trx with id 12598913, 357 rows to undo
2017-06-29 13:06:01 54072 [Note] InnoDB: Waiting for purge to start
2017-06-29 13:06:01 54072 [Note] InnoDB: 5.6.35 started; log sequence number 7906092439081
2017-06-29 13:06:01 54072 [Note] Recovering after a crash using /var/lib/mysql/bin-log
2017-06-29 13:06:05 54072 [Note] Starting crash recovery...
2017-06-29 13:06:05 7f4358cf4740 InnoDB: Starting recovery for XA transactions...
2017-06-29 13:06:05 7f4358cf4740 InnoDB: Transaction 12598911 in prepared state after recovery
2017-06-29 13:06:05 7f4358cf4740 InnoDB: Transaction contains changes to 3890 rows
2017-06-29 13:06:05 7f4358cf4740 InnoDB: 1 transactions in prepared state after recovery
2017-06-29 13:06:05 54072 [Note] Found 1 prepared transaction(s) in InnoDB
2017-06-29 13:06:05 54072 [Note] InnoDB: Rollback of trx with id 12598913 completed
2017-06-29 13:06:05 7e59c4317700 InnoDB: Rolling back trx with id 12598910, 1364 rows to undo

InnoDB: Progress in percents: 12017-06-29 13:06:05 54072 [Note] Crash recovery finished.
2 3 42017-06-29 13:06:08 54072 [Note] Server hostname (bind-address): '*'; port: 3306
2017-06-29 13:06:08 54072 [Note] IPv6 is available.
2017-06-29 13:06:08 54072 [Note] - '::' resolves to '::';
2017-06-29 13:06:08 54072 [Note] Server socket created on IP: '::'.
2017-06-29 13:06:08 54072 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode.
2017-06-29 13:06:08 54072 [Warning] 'user' entry '@localhost.localdomain' ignored in --skip-name-resolve mode.
2017-06-29 13:06:08 54072 [Warning] 'db' entry 'monitor ggs_owner@locahost' ignored in --skip-name-resolve mode.
2017-06-29 13:06:08 54072 [Warning] 'proxies_priv' entry '@ root@localhost.localdomain' ignored in --skip-name-resolve mode.
52017-06-29 13:06:08 54072 [Note] Event Scheduler: Loaded 0 events
2017-06-29 13:06:08 54072 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.35-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 1002017-06-29 13:06:35 54072 [Note] InnoDB: Rollback of trx with id 12598910 completed
2017-06-29 13:06:35 7e59c4317700 InnoDB: Rolling back trx with id 12598908, 1602 rows to undo

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.