… I explained how to repair MySQL 5.6 GTID replication using two different …error: Last_SQL_Error: Error ‘Duplicate entry ‘4‘ for key ‘PRIMARY” on query. Default database: ‘test…table-checksum can help you here, which is found in Percona Toolkit for MySQL. Last week I gave a talk at Percona MySQL…
Post: Benchmarking Percona Server TokuDB vs InnoDB
… KEY (hid,mid,id) ). Also please note the transaction produces 4 INSERTs and workload is very write intensive. So what are…: sysbench –test=insert_roll.lua –oltp-table-size=10000 –mysql-user=root –oltp-tables-count=32 –mysql_table_engine=tokudb –oltp_auto_inc=on –max…_file_size = 10G myisam_repair_threads = 1 myisam_recover socket=/var/lib/mysql/mysql.sock user=root skip-grant-tables TokuDB-related options are…
Post: Virident vCache vs. FlashCache: Part 2
…. EXT4 is the filesystem, and CentOS 6.4 the operating system, although the pre-release …=95 \ –mysql-user=root –mysql-socket=/tmp/mysql.sock –mysql-table-engine=innodb \ –oltp-read-only=off run The base MySQL configuration… 8M myisam_max_sort_file_size = 10G myisam_repair_threads = 1 …
Post: Aligning IO on a hard disk RAID – the Benchmarks
… with different IO alignment, not different MySQL configurations, I didn’t try out different MySQL versions or settings. Moreover, I…_max_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover skip-grant-tables Amount of rows used was 20M,…} dm-0 447.1 34.0 7.4 0% 2.4 5.4 23.4 49.6 0.6 0% 0.0…
Post: Adventures in archiving
…_format=compressed key_block_size=4 4.04:1 648M compress() 1….attempting a table checksum. #57188 Repair tools will not function on Archive tables. #62054 …mysql> select id from archive_table order by id desc limit 1; +———+ | id | +———+ | 1143883 | +———+ 1 row in set (2.04 sec) mysql…
Post: MySQL Crash Recovery
… – users may issue different queries which may trigger check/repair running for many tables at onces, which typically make system extremely slow… innodb-safe-binlog option in MySQL 4.1 so your Innodb log and binary log are synchronized. In MySQL 5.0 XA is… unsync with internal Innodb dictionary may cause MySQL to fail with wierd error messages. In MySQL 4.1 sync_frm option was added…
Post: MySQL optimizer: ANALYZE TABLE and Waiting for table flush
…TABLE: mysql> analyze table t; +——–+———+———-+———-+ | Table | Op | Msg_…table flush | select * from test.t where i=4 | | 11 | Waiting for table…TABLES, ALTER, RENAME, OPTIMIZE or REPAIR can cause threads to wait on “Waiting for tables“, “Waiting for table” and “Waiting for table…
Comment: Upgrading MySQL
… table index format in MySQL 5.0. Upgrade from MySQL 4.1 to 5.0 and repair all MyISAM tables (see Section 2.4.4, “Rebuilding or Repairing Tables or Indexesâ€). Then upgrade from MySQL 5…
Post: MySQL MyISAM Active Active Clustering - looking for trouble ?
… repair before you can safely use it, which takes long time for large tables. Furthermore as I remember MySQL simply was not repairing corrupted tables in this configuration even if myisam_repair is set. Space… even query cache which was implemented many years ago in 4.0 was implemented without looking at this feature, so what…
Comment: Should you move from MyISAM to Innodb ?
… table parsing. In that case, I suspect you will certainly NOT have the time for a REPAIR TABLE on your MyISAM’s corrupted table…. On average, 5 days each week are consumed by REPAIR TABLE. The larger tables take 4-5 *days* to restore. Please be prepared for… the right choice. You’ve has a review by a MySQL consultant. I’m assuming the review was professional. But you…

