Shulou(Shulou.com)05/31 Report--

Mysql replication slave server data delay reasons and solutions, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

The causes and Solutions of data delay in replicating slave Server

The inherent reason for the delay is that the master server has two threads from the slave server, but can only be executed sequentially by a single thread.

In addition, there are also reasons such as network delay.

Cause of delay:

The master server can execute in parallel with multiple threads, while the slave server cannot execute in parallel because there are two processes that need to depend on each other.

Long execution of queries due to inefficient join operations.

Hard drive IO bottleneck.

Data lock.

InnoDB concurrent thread problem.

Solution to delay: www.2cto.com

1. Organize your data effectively: data regularization, data partitioning.

Divide and conquer, breakthroughs: enough slave; when all slave lag (delay)

Replication filtering and intermediary slave are required

3. Find out the long-running query and construct the query: simplify the query or replace it with a transaction.

When using transactions, consider data loss due to slave execution.

4. Load balancing.

5. Keep the hardware up to date.

6. Reduce lock contention: MyISAM lock table and InnoDB row-level lock.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.