June 20, 2013

Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

… untracked log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the log parser… to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the…/O error if changed page tracking is enabled. Bug fixed #1184517. The INNODB_CHANGED_PAGES table couldn’t be queried if the log

Post: Choosing a MySQL HA Solution - Post-Webinar Q&A

… specified set of databases and tables. With this method, every event is still written to the binary log on the master, but… executed on the intermediate server, thus resulting in less binary log data being sent down to the lower-level slaves. You…” errors. I was able to get the server up with –skip-grant-tables and insert a few rows into an InnoDB table, but…

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

… #1181887. Changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive… to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the…. Bug fixed #1185040. The INNODB_CHANGED_PAGES table couldn’t be queried if the log tracker wasn’t running. Bug fixed #1185304…

Post: Migrating between MySQL schemas with Percona Xtrabackup

… Ensure innodb_import_table_from_xtrabackup = 1  (dynamic variable) Prepare the backup using the –export flag:  innobackupex –apply-log –export /tmp/snapshot/2013-06-03_11-30 For each table, run:  ALTER TABLE tblname DISCARD TABLESPACE Copy… you to compare and restore values (potentially corrupted via user error or other issues) with SQL rather than needing to import…

Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency

…=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size…=myisam tmpdir=/dev/shm innodb_undo_logs=32 innodb_old_blocks_time=0 table_open_cache=2048 table_definition_cache=16384 innodb_flush… innodb_stats_persistent innodb_stats_auto_update=off [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid

Post: Benchmarking Percona Server TokuDB vs InnoDB

…_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log… (fixed) port = 3306 back_log = 50 max_connections = 2000 max_prepared_stmt_count=500000 max_connect_errors = 10 table_open_cache = 2048 max_allowed_packet = 16M binlog_cache_size = 16M max_heap_table_size = 64M sort…

Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

…: Yes [...] The error log tells us why the IO thread has not started: 2013-05-17 13:21:26 3130 [ERROR] Slave I… GTID_MODE ON and this server has GTID_MODE OFF, Error_code: 1593 These simple tests answer the first two questions… slave; and let’s create a new table on the master: mysql> create table test.t (id int not null auto_increment…

Post: Virident vCache vs. FlashCache: Part 2

…_per_table = true innodb_data_file_path = ibdata1:100M innodb_flush_method = O_DIRECT innodb_log_buffer_size = 128M innodb_flush_log_at… (fixed) back_log = 50 wait_timeout = 120 max_connections = 5000 max_prepared_stmt_count=500000 max_connect_errors = 10 table_open_cache = 10240 max_allowed_packet = 16M binlog_cache_size = 16M max_heap_table_size = 64M sort…

Comment: Follow these basics when migrating to Percona XtraDB Cluster for MySQL

… 2. BUT every time i do an update in a table, the write is not propagated to the other nodes, even… statements such as table creation are! any idea of what’s going on? i turned all sorts of logging on and i keep seeing: “Skipping empty log_xid” messages in error log, but not affecting the tables im testing so…

Post: Percona XtraBackup 2.0.7 for MySQL available for download

… prevent XtraBackup failures that are caused by the log records in the transactional log being overwritten before they are copied by the… log files were bigger than 4G on the source server. Bug fixed #1164979. Due to different implementation in MySQL 5.6 error… InnoDB error or diagnostic messages are never printed by xtrabackup_56. Bug fixed #1169971. innobackupex would still run with FLUSH TABLES WITH…