Skip to main content

MySQL multi thread master slave replication

MySQL multi thread master slave replication:

In Multi-thread slave replication transactions are split per MTS thread (multiple sql threads processing events from the relay log) based on the database/schema. If you have one schema there will be no benefit as there is nothing or little to split between worker threads. Multi-thread replication helps environments with lots of databases, each database is writing heavily and the writes can be split between worker threads. Order of updates on a database are the same as they are on the master.
For cross-database transactions, the slave waits until all preceding transactions that are working on the same database set are over.

Enable Multi-thread Master slave replication:
01. Set following parameters on Slave in /etc/my.cnf file:
master-info-repository = TABLE
slave-parallel-workers = 2
relay-log-info-repository = TABLE
02. Check exisiting parameter value
mysql> show global variables like "%repository%";
+---------------------------+-------+
| Variable_name | Value |
+---------------------------+-------+
| master_info_repository | TABLE |
| relay_log_info_repository | TABLE |
+---------------------------+-------+
03. Set slave paraller workers.
mysql> set global slave_parallel_workers=4;
mysql> stop slave;
mysql> start slave;
mysql> show slave status \G;

Preserver Master commit order on slave require following parameters:
01. Enable slave_perserver_commit_order on slave ensures the order which transactions were committed on the master is preserved on the slave.
mysql>  set global slave_perserver_commit_order=ON;
02. Make sure binlog_order_commits is ON.
mysql> show variables like '%binlog_order%';
+----------------------+-------+
| Variable_name        | Value |
+----------------------+-------+
| binlog_order_commits | ON    |
+----------------------+-------+
03. Enable slave paraller workers
mysql> set global slave_parallel_workers=4;
mysql> stop slave;
mysql> start slave;
mysql> show slave status \G;

Ref. https://mysqlhighavailability.com/preserve-masters-commit-order-on-slave/






Comments

  1. MySQL multi-threaded master-slave replication significantly improves performance by allowing concurrent processing of multiple replication threads. Explore the benefits and implementation strategies to optimize your database setup with hostingmella!

    ReplyDelete

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

Amazon RDS | Amzon Redshift | Big Data | Boost Performance with Amazon ElastiCache

Amazon RDS with Amazon ElastiCache for Performance: Amazon RDS supports - Oracle, MS SQL server, MySQL, Maria DB and PostgreSQL. It is a managed service offered by the Amazon.  Couple of customers have observed the performance issues during their journey with Amazon RDS with Oracle, MS SQL Server, MySQL, Maria DB and PostgreSQL. Amazon cloud engineers / database consultants / database architect and Amazon supports worked to-gather to boost the Amazon RDS performance by tuning the RDBMS configuration parameters using Amazon RDS parameter group , and have not achieved the SLA for Amazon RDS .  Amazon RDS with Multi AZ and Read Replica: Some of the the AWS professionals have suggested for vertical scaling of the Amazon RDS . It should works and its absolutely correct. In my opinion, it would be a good idea to think about the Amazon ElastiCache service with Amazon RDS for better performance and cost optimization also rather than vertically scaling the Amazon RDS . I would sug...

Needs for Graph Database

Needs for Graph Database: We are living in the era of data, data is treated more precise than gold and platinum. Most of the enterprises are trying to get more insight about the data they have it as an operational / warehouse / analytical.   Ref.: https://dist.neo4j.com/wp-content/uploads/graph-example.png To get more insight into the data, it is required to see the relationship among the data points. The challenge is how to establish the relationship among data points and the answers is Graph database. Relational databases can't help to establish the relationship among data points, due to their rigid schema, and consistent schema. Relational Database issues for data set: Number of Joins:  While fetching data from relational databases, we join many tables, these joins are complex, and consume considerable amount of computing resources, which increase the query response times. Self- joins: For database ware house / business intelligence systems using RDBMS, self-JOIN are ...