… to be on the safe / perfect side. innodb_log_file_size is always a fixed parameter and it is quite difficult to extend… x 4 = 128M innodb_buffer_pool_size). According to my previous posts in this blog a dynamic innodb log file RECREATE did NOT seem to work if you are going to delete the log files later (or…
Post: ext4 vs xfs on SSD
March 15, 2012 By 23 Comments
…ext4 has an option dioread_nolock, which supposedly fixes that, but that option is not available on…point to consider. Starting the MySQL 5.1 + InnoDB-plugin and later MySQL 5.5 (or equally…-init=on –file-num=1 –file-extra-flags=direct –file-fsync-freq=0 –file-io-mode=sync –file-block-size=16384 …
Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables
March 26, 2012 By 20 Comments
Kristian – this is worth fixing if that is a bug in InnoDB. Can you file one at bugs.mysql.com with details from… log? AFAIK, InnoDB is snapshot safe as long as database files and log files are on the same filesystem. But MySQL/InnoDB is not snapshot safe if DDL operations are in flight because DDL between MySQL (frm files) and InnoDB is not…
Post: Troubleshooting MySQL Memory Usage
March 21, 2012 By 3 Comments
… 7234 TABLE_SCHEMA: test TABLE_NAME: my ENGINE: InnoDB NAME: #sql516_1c42_2 TABLE_ROWS: 0…) Page hash 127499384 Dictionary cache 512619219 (509995888 + 2623331) File system 294352 (82672 + 211680) Lock system 318875832 (318747272 …and when it can be found and fixed. This is where your MySQL Support …
Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables
March 24, 2012 By 20 Comments
… either not having log files and data on the same partition or synchronization of binary log and innodb snapshot. In certain versions…” operation which caused wrong binary log positions but it is fixed now at least in 5.5
Post: Connecting orphaned .ibd files
May 13, 2011 By 12 Comments
… ibdata files. A well known innodb_file_per_table option brings the second one. Tables and system areas are split into different files. Usually system tablespace is located in ibdata1 file and every InnoDB table has two files e.g. actor.frm…) page 11: new style: calculated = 0x E4189B9B; recorded = 0x C168689B fixing new checksum of page 11 # # ./innochecksum -f /var/lib/mysql…
Post: XtraDB/InnoDB CPU bound benchmarks on 24cores server
December 29, 2008 By 6 Comments
… ready soon. Main difference XtraDB-rel2 it contains additional scalability fixes for buffer_pool (split_buffer_pool_mutex patch). my.cnf…=15G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=512M innodb…
Post: Another scalability fix in XtraDB
January 23, 2009 By 13 Comments
… fixes in InnoDB and also Google’s and your SMP fixes almost made InnoDB results acceptable in primary key lookups queries,…innodb_log_file_size=128M \ –innodb_log_files_in_group=2 \ –innodb_log_buffer_size=8M \ –innodb_flush_log_at_trx_commit=2 \ –innodb_thread_concurrency=16 \ –innodb_file…
Post: Reasons for run-away main Innodb Tablespace
June 10, 2010 By 1 Comment
So you’re running MySQL With innodb_file_per_table option but your ibdata1 file which holds main (or system) tablespace have grown… Write Buffer is fixed size (2MB = 128 of 16KB pages) and so will not affect growth of your main Innodb Tablespace. Insert… as I would like. I filed number of feature requests and I hope we’ll have a chance to fix this soon.
Post: Lost innodb tables, xfs and binary grep
November 9, 2010 By 11 Comments
… lost: MySQL had a dedicated partition on XFS file system Server was running innodb_file_per_table There was a production master and… file recovery tools for xfs – apparently they are all targeting specific file types and sure enough InnoDB is not one of the supported files…, but it really wasn’t – all of the columns were fixed size – 2bytes each, so the thing we had to look…
