June 18, 2013

Comment: Database problems in MySQL/PHP Applications

….info file, and any later # change in this file to the …info file, unless you shutdown # the slave server, delete master…size innodb_log_file_size = 1000M #innodb_log_buffer_size = 32M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql

Comment: How to calculate a good InnoDB log file size

mysql/ innodb_log_arch_dir = /var/lib/mysql/ innodb_buffer_pool_size = 2048M innodb_additional_mem_pool_size = 20M innodb_log_file_size = 512M innodb_log_files_in_group = 2 innodb_log_buffer_size = 8M innodb_thread_concurrency = 8 innodb

Comment: How to change innodb_log_file_size safely

log file size. On my system I set to 128M, which does not 100% accurately reflect log file size x 4 factor. But I can changeinnodb_log_file_sizeinnodb log file RECREATE did NOT seem to work if you are going to delete the log files

Post: Recovering Innodb table Corruption

innodb_force_recovery=1 and as you can see even though I get the message in the log filedeleted rows or dropped table. I should also mention at Percona we offer assistance in MySQL Recovery, including recovery from Innodb corruptions and deleted

Post: Tuning InnoDB Concurrency Tickets

DELETE CASCADE -> ) ENGINE=INNODB; — 0 Tickets Used Query OK, 0 rows affected (0.00 sec) mysqlsize=24G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 8M innodb_log_files_in_group=2 innodb_log_file_size=1900M innodb

Post: Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs

InnoDB, it is also important that your transaction logsmysql> show binary logs; +——————+———–+ | Log_name | File_size | +——————+———–+ … | mysql-bin.000022 | 336797725 | | mysql-bin.000023 | 107 | +——————+———–+ 23 rows in set (0.00 sec) mysql

Post: How would you compress your MySQL Backup

innodb hot backup or snapshot backup) as this is only way practical at this point for databases of decent sizefile size. Though in this example we used MySQL binary log filedelete this particular file. BZIP compression for this file took 298 seconds which is just 3.4 MB/sec though compressed file

Post: Why you can't rely on a replica for disaster recovery

files. After running fsck on the replica, the InnoDB data files were entirely deletedInnoDB file” contained blocks of data that were obviously from other files, such as Python exception logschangedMySQL replication has the same weakness. If you rely on a MySQL

Comment: MySQL Server Memory Usage

size=20M innodb_file_io_threads=4 innodb_lock_wait_timeout=15 # CHANGED from 50 innodb_log_files_in_group=3 innodb_flush_log_at_trx_commit=0 #innodb_log_file_size

Post: Paul McCullagh answers your questions about PBXT

… to innodb_flush_log_at_trx_commit=2). A major change was completed…are no longer needed and deletes them from the database. The…sizes can be set using compile time switches. However, if the index page size is changed….frm file. One extreme example of this is PBXT recovery. When MySQL calls the…