June 18, 2013

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

Global Transactions Identifiers are one of the new features regarding… TO to instruct all servers to use GTIDs Disable read-only mode This procedure will switch all your servers from … replication modes on different servers, but only if all servers have gtid_mode set to ON. Could it be interesting …

Post: Galera Flow Control in Percona XtraDB Cluster for MySQL

…in a master/slave cluster might be: mysql> set global wsrep_provider_options=”gcs.fc_limit=500; … have applying cluster transactions. Therefore, it keeps reads more up to date without needing to …. EDIT: actually the cost of certification depends only the size of the transactions, which translates …

Comment: How to know if you're updating Slave you should not ?

Dmitriy: You can use SET GLOBAL read_only=1/0

Post: How fast is FLUSH TABLES WITH READ LOCK?

read-onlyread and written. The first write query to each table will immediately block against the requested global read lock, and subsequent read… 4 rows in set

Post: Percona XtraDB Cluster: Failure Scenarios with only 2 nodes

… | ON | | wsrep_local_index | 1 | | wsrep_ready | ON | only wsrep_local_index defers as expected. …kenny | +—-+—————+——–+ 2 rows in set (0.00 sec) Adding ignore quorum and restart both nodes: set global wsrep_…07-24 11:42:50.237 INFO: Read config: daemon: 0 address: gcomm://192….

Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

READ LOCK to temporary make MySQL read only. In many cases the period for which server has to be made read only… with read lock | 0 | 0 | 1 | | 10291 | root | localhost | dumptest | Query | 74 | Waiting for global read lock …design) for read lock to wait for other read lock in order to be set. As …

Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

set (0.00 sec) Now compare the difference with innodb_old_blocks_time=0; mysql> set global

Post: How to create/restore a slave using GTID replication in MySQL 5.6

…: slave> set global GTID_EXECUTED=”9a511b7b-7059-11e2-9a24-08002762b8af:1-14″ ERROR 1238 (HY000): Variable ‘gtid_executed’ is a read only variable Error! Remember, we get the GTID_EXECUTED from the master and set is as GTID_PURGED on the slave. slave1 > set global

Post: Can we improve MySQL variable handling ?

read it: mysql> set global sort_buffer_size=DEFAULT; Query OK, 0 rows affected (0.00 sec) mysql> select @@global.sort_buffer_size; +—————————+ | @@global

Post: How much overhead is caused by on disk temporary tables

… 7248 | | Key_read_requests | 2051451 | | Key_reads | 198208 | | Key_write_requests | 469220 | | Key_writes | 185808 | +————————+———+ 7 rows in set (0…mysql> set global tmp_table_size=1000000000; Query OK, 0 rows affected (0.00 sec) Ahh… I alway forget GLOBAL only sets global