… the downsides to mysqldump is the need to scan the full tables and in turn, load that data into and pollute….TABLES WHERE TABLE_SCHEMA=’orig’ AND ENGINE=’InnoDB’; EOF For full disclosure, here are the versions I was using on my…
Post: How to fix your PRM cluster when upgrading to RHEL/CentOS 6.4
May 29, 2013 By 2 Comments
…, 3 expected votes 7 Resources configured. Online: [ percona1 percona2 percona3 ] Full list of resources: reader_vip_1 (ocf::heartbeat:IPaddr2): Started…, 3 expected votes 7 Resources configured. Online: [ percona1 percona2 percona3 ] Full list of resources: reader_vip_1 (ocf::heartbeat:IPaddr2): Started…
Comment: ZFS on Linux and MySQL
May 28, 2013 By 17 Comments
… XFS uses transactional model, metadata checksums may be sufficient. With full data checksums there are going to be penalties – with both…
Comment: ZFS on Linux and MySQL
May 28, 2013 By 17 Comments
… the latest zfsonlinux. c) metadata checksum is way short than full data checksum. d) I compared lzjb (default), lz4, gzip-1…
Comment: What Are Full, Incremental, and Differential Backups?
May 22, 2013 By 9 Comments
… backup e.g. A backup done once per week using full on the first week, then incremental for 7 weeks thereafter…
Comment: Benchmarking Percona Server TokuDB vs InnoDB
May 22, 2013 By 32 Comments
Does Percona have improvements to keep the InnoDB insert buffer from getting full (as in do background reads for ibuf merges when it is getting full)? That is the key to sustaining good throughput for InnoDB on iibench.
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… still get the deadlock error. This is not implemented for full BEGIN … COMMIT multi-statement transactions since it cannot be assumed…
Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download
May 7, 2013 By Leave a Comment
… writing). New Features: This version of Percona XtraBackup has implemented full support for new MySQL 5.6 features (GTID, remote/transportable… that were dropped between taking a full backup and an incremental one were present in the full backup directory, and were not…
Comment: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
… overhead in PK rows * PK index pages are 15/16 full as they are loaded in order * 7 bytes per-row… overhead for secondary index entries * fragmented pages are 2/3 full So my guess is: * 50G for PK index * 6G for…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
… can’t make 5h run. After 3h the disk is full, and InnoDB data size is about 210GB with 234.238…
