… later the lock algorithm for the auto_increment value is configurable and you can select from different algorithms using the innodb_autoinc_lock_mode. By… is possible to return to the traditional method changing the innodb_autoinc_lock_mode to 0. But with a loss of performance and concurrency. How…
Post: InnoDB auto-inc scalability fixed
… we had a lot of customers who was affected by InnoDB auto-inc. For several of them we even advised to… if the fix is going to be ported to 5.0, as I mentioned it affected many production systems and not… is the fix introduces new system variable innodb_autoinc_lock_mode which determines behavior of InnoDB for tables with autoinc. I do not want to copy…
Post: Innodb usability and ease of use.
… in hard to parse SHOW INNODB STATUS output or even uglier hacks with creating tables such as innodb_lock_monitor to get more… file – For example using values “none”, “disk”, “os” instead of 0,1,2 will be more explanatory. Furthermore MySQL even has…_DIRECT, O_DSYNC, fdatasync etc. However Look at new variable innodb_autoinc_lock_mode freshly added in 5.1.22 (which is what motivated…
Post: Announcing Percona Server 5.1.65-14.0
… tracking thread. HandlerSocket has been upgraded to version 1.1.0. Bugs Fixed: Loading LRU dump was preventing shutdown. Bug fixed… being updated rather than inserted) with the default value of innodb_autoinc_lock_mode=1. Bug fixed #1035225 (Alexey Kopytov). Since the output file…
Post: Announcing Percona Server 5.5.27-28.0
… announce the release of Percona Server 5.5.27-28.0 on August 23rd, 2012 (Downloads are available here and from… default value of innodb_autoinc_lock_mode=1. Bug fixed #1035225 (Alexey Kopytov). Removed error log warnings that occured after enabling innodb_use_sys_stats… setting up the innodb_lazy_drop_table to 1. Release notes for Percona Server 5.5.27-28.0 are available in…
Post: Percona XtraDB Cluster reference architecture with HaProxy
…-112-39-98 log_slave_updates innodb_locks_unsafe_for_binlog=1 innodb_autoinc_lock_mode=2 innodb_buffer_pool_size=400M innodb_log_file_size=64M You… server = /usr/bin/clustercheck log_on_failure += USERID only_from = 0.0.0.0/0 # recommended to put the IPs that need # to connect exclusively…
Post: Investigating MySQL Replication Latency in Percona XtraDB Cluster
… statement on the different cluster node: per-request statistics: min: 0.69ms avg: 1.12ms max: 52334.76ms approx. 95 percentile… wsrep_cluster_name=DPE binlog_format=ROW default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 innodb_locks_unsafe_for_binlog=1 wsrep_sst_auth=root:
Comment: MySQL on Amazon RDS part 2: Determining Peak Throughput
… innodb_additional_mem_pool_size 2097152 innodb_autoextend_increment 8 innodb_autoinc_lock_mode 1 innodb_buffer_pool_size 55050240000 innodb_change_buffering inserts innodb_checksums ON innodb_commit_concurrency 0 innodb_concurrency_tickets 500 innodb_data…
Comment: Avoiding auto-increment holes on InnoDB with INSERT IGNORE
…. # =0 is traditional lock mode == > funcionality of auto_increment like before 5.1.22 # =1 is default value – consecutive lock mode # =2 is interleaved lock mode , i don’t investigate what it do innodb_autoinc_lock_mode=0 2. restart mysql server now…
Comment: Solving RPM installation conflicts in CentOS 5 and CentOS 6
… wsrep_sst_method=rsync wsrep_node_name=mysql1 innodb_locks_unsafe_for_binlog=1 innodb_autoinc_lock_mode=2 the wrong infomaton : 130221 17:59:00… no messages after this, something went terribly wrong… stack_bottom = 0 thread_stack 0×30000 /usr/sbin/mysqld(my_print_stacktrace+0×33…

