The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

High Latency Issue between Master -> Slave (MariaDB)

We are facing latency issues between Master and 2 Slave DB's.

Platform - GCP Installation - GCP Marketplace - MariaDB with Replication

Server Config - n1-standard-4 (4 vCPUs, 15 GB memory) Location - Mumbai Region, India

Following are the queries we have:- 1. If we increase the server config (vCPU's, Memory and HDD) will it help us with improving "latency" between Master and Slave 2. Is there a way we can avoid syncing of specific tables on slave? We want to avoid syncing log tables which has a lot of data. 3. We use Opencart with Redis/Elastic but the number of workers/crons running choke the db, hence what config is recommended? 4. If we move to CloudSQL will it help in improving the master>slave latency issues?

Answer Answered by Ian Gilfillan in this comment.

2) You can ignore specific tables or databases, with the replicate_ignore_db, replicate_ignore_table and related variant options. You can also selectively skip certain binlog items, as well as implement Parallel Replication.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.