I’m glad to announce the third Percona Playback release – another alpha release of a new software package designed to replay database server load. The first two versions were released in April, just in time for my talk at the Percona Live MySQL Conference and Expo: Replaying Database Load with Percona Playback. This is still […]
In this post I want to show new possibilities which open with Percona XtraDB Cluster. We will create 3 nodes Cluster with nodes on different continents (Europe, USA, Japan) and each node will accept write queries. Well, you theoretically could create 3 node traditional MySQL ring replication, but this is not what you want to […]
Codership team published beta2 of MySQL 5.5.15 with Galera replication https://launchpad.net/codership-mysql and we made port to Percona Server: source code: lp:~percona-dev/percona-server/percona-server-galera-5.5.15 binaries for RedHat/CentOS 6: http://www.percona.com/downloads/TESTING/Galera/Percona-XtraDB-Galera-5.5.15.tar.gz What difference between Percona Server+Galera and MySQL 5.5.15 ? First of course, Percona Server+Galera is based on our XtraDB engine. Second, we provide wsrep_sst_xtrabackup script, which allows to use […]
Codership team announced availability of MySQL/Galera 0.8.1, which is minor release, but actually it has bunch of improvements that makes Galera replication more user friendly (there are many bugs fixed, reported by me personally, what annoyed me a lot). As part of my evaluation activity I ported MySQL/Galera 0.8.1 to Percona Server/Galera 0.8.1 and you […]
Previously I covered simple case with FlashCache, when data fits into cache partitions, now I am trying to test when data is bigger than cache. But before test setup let me address some concern (which I also had). Intel X25-M has a write cache which is not battery backuped, so there is suspect you may […]
I wrote about FlashCache there, and since that I run couple benchmarks, to see what performance benefits we can expect. For initial tries I took sysbench oltp tests ( read-only and read-write) and case when data fully fits into L2 cache. I made binaries for FlashCache for CentOS 5.4, kernel 2.6.18-164.15, you can download it […]
Dear Community, The build 17 of MySQL with Percona patches is available. New features in the release: MySQL-5.0.83 is taken as the basis The new patch innodb_use_sys_malloc.patch is added The new patch innodb_split_buf_pool_mutex.patch is added This patch splits the single global InnoDB buffer pool mutex into several mutexes for different purposes. This reduces mutex contention. […]
We announce next version of our xtrabackup tool and we consider it stable enough to put label RC on it. Changelist includes: – use O_DIRECT by default for handling InnoDB files – use posix fadvise call to disable OS caching of copying files – disable recovery of double buffer Also we added binary builds for […]
We announce next beta version of our xtrabackup tool. Changelist includes: – set innodb_fast_shutdown=1 on xtrabackup shutdown – set innodb_write_io_threads=10 by default for fast buffer_pool flushing during recovery – build xtrabackup with –with-extra-charsets=complex Bug #357653: innobackupex-1.5.1 –copy-back fails Bug #358194: 2nd-phase is very slow Bug #358266: xtrabackup-0.5 dies with SEGV on bad command line arguments […]
I am happy to announce next build of our backup tool. This version contains several bugfixes and introduces initial implementation of incremental backup. Incremental backup works in next way. When you do regular backup, at the end of procedure you can see output:
The latest check point (for incremental): '1319:813219999'
>> log scanned up to (1319 813701532)
Transaction log of lsn (1318 3034677302) to (1319 813701532) was copied.
090404 06:03:29 innobackupex: All tables unlocked
090404 06:03:29 innobackupex: Connection to database server closed
innobackupex: Backup created in directory '/mnt/data/tmp'
innobackupex: MySQL binlog position: filename 'db02-bin.001271', position 247627478
090404 06:07:58 innobackupex: innobackup completed OK!
innobackupex: You must use -i (--ignore-zeros) option for extraction of the tar stream.
which gives start point 1319:813219999 for further incremental backup. This point […]