Bug #75890 A new feature request of slave mts apply

• Submitted: 13 Feb 2015 9:41
• Reporter: Fangxin Flou (OCA)
• Status: Open
• Category: MySQL Server: Row Based Replication ( RBR )
• Severity: S4 (Feature request)
• Version: 5.6.x
• OS: Any
• CPU Architecture: Any
• Tags: binlog, MTS

[13 Feb 2015 9:41] Fangxin Flou

Description:
I checked the logic of MTS in 5.6, the binlog event is grouped into different worker queues by database name, so we must put many many tables into different databases, it not so good for us. 

In real world, we usually split big tables into few small tables in MySQL with a different suffix. For example we have tables "orders" and "orders_line", we always put this two tables into one transaction, it's splited into several pieces, such as:

orders_0
orders_line_0

orders_1
orders_line_2

orders_1
orders_line_2

so we could group the binlog event accord to the suffix, all events without suffix will map to a fixed worker queue, for events with suffix group them by the suffix.

The logic is very reasonable and it's a good way to parallelize the binlog SQL relay.

Thanks.

How to repeat:
This is feature request

Suggested fix:
This is feature request

[18 Sep 2015 9:20] Venkatesh Duggirala

In MySQL-5.7.2,  MySQL enhanced MTS (Multi-threaded slave) and it can be used to apply transactions in parallel even within a single database. 

Please have a look at 

https://dev.mysql.com/doc/refman/5.7/en/replication-options-slave.html#option_mysqld_slave...

for more details about the option.

[29 Nov 2019 8:14] WANG GUANGYOU

should close this feature now! Mr Lou!