lp:~stewart/percona-server/5.6-doublewrite

Created by Stewart Smith and last modified
Get this branch:
bzr branch lp:~stewart/percona-server/5.6-doublewrite
Only Stewart Smith can upload to this branch. If you are Stewart Smith please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Recent revisions

310. By Stewart Smith

Port innodb_doublewrite_file to Percona Server 5.6

This was a little bit involved as the doublewrite buffer code has been
refactored in MySQL 5.6 out into buf0dblwr.cc.

One design difference in the 5.6 patch versus 5.5 and before is that where
InnoDB code has needed to be duplicated, I have instead refactored that code
to accept tablespace id as a parameter rather than copy&pasting it. With
this method, we should get merge conflicts if this code is changed upstream,
making it easier to ensure our end result code is correct.

309. By Stewart Smith

merge 5.6.7

308. By Stewart Smith

document that LRU dump/restore is replaced with MySQL implementation

307. By Stewart Smith

null merge innodb_lru_dump_restore.patch from PS5.5. Relpaced by MySQL functionality

306. By Stewart Smith

null merge innodb_extend_slow.patch from PS5.5. We're going to replace it with a plugin, possibly omitting some of the extended InnoDB parts

305. By Stewart Smith

merge null-merge of show-lock-name patch

304. By Stewart Smith

merge show temp tables test fixes

303. By Stewart Smith

null merge innodb_admin_command_base.patch as it was only used for manual LRU dump/restore and this is now native in MySQL 5.6

302. By Stewart Smith

null merge innodb_recovery_patches.patch - two bug fixes have been broken out into separate commits and we aren't bringing innodb_recovery_stats forward to PS 5.6

301. By Stewart Smith

Extract fix for http://bugs.mysql.com/bug.php?id=44140 from innodb_recovery_patches.patch

Description from original bug report:
Description:
Sometimes (it is really rare), We meet the error message during crash recovery of InnoDB.

090405 4:29:47 InnoDB: ERROR: We were only able to scan the log up to 1319 813701532
InnoDB: but a database page a had an lsn 1319 814039859. It is possible that the
InnoDB: database is now corrupt!

I accept the message as,,
"There have been some logged modification to certain page before the last recv_recover_page() for the page"

And I have caught the modification.
#0 0x00000000004a5b60 in log_close ()
#1 0x00000000004d93b9 in mtr_commit ()
#2 0x000000000042e572 in ibuf_delete_rec ()
#3 0x000000000042f314 in ibuf_merge_or_delete_for_page ()
#4 0x000000000049724e in buf_page_io_complete ()
#5 0x00000000004cbdd7 in fil_aio_wait ()
#6 0x000000000040c678 in io_handler_thread ()

I suspect ibuf_merge_or_delete_for_page() from buf_page_io_complete() (triggered by recv_read_in_area()) and recv_recover_page() from recv_apply_hashed_log_recs() can conflict.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:percona-server/5.5
This branch contains Public information 
Everyone can see this information.

Subscribers