Bobcares

MariaDB replicate do db | Beginners Guide

by | Aug 6, 2022

MariaDB replicate do db is a replication Filter option for MariaDB. We answer all questions, no matter how big or small, at Bobcares as part of our Server Management Services.

What is MariaDB replicate do db?

We can configure a replication slave to apply statements and transactions affecting databases that match a given name by setting the replicate do db system variable. Replicate do-db instructs the slave to only read relay log entries for the specified database. Since there is no relay log to read from, replicate do db has no impact on the master. The lock tables component ensures that the data is reliable.

The system will not work for:

  • Cross-database updates with statement-based logging
  • Mixed-based logging and the statement is logged statement based

Only the default database (i.e., the one chosen by USE) and not any explicitly mentioned tables in the query are taken into account for statement-based replication. When an event login its statement-based format, replicate do db will test the filter against the default database.

However, The system variable will accept a list of filters when set dynamically with SET GLOBAL. It is not possible to specify database names that contain commas while setting it dynamically. So to specify database names with commas, they must be specified via command line options. When setting it dynamically, the slave threads must stop.

Example:

STOP SLAVE;
SET GLOBAL replicate_do_db='db1,db2';
START SLAVE;

The system variable does not accept lists that separate each other by a comma when set via the command line. So to specify the system variable more than once if we need to specify multiple filters.

Example:

[mariadb]
...
replicate_do_db=db1
replicate_do_db=db2

The slave will do the following:

  • Replicate the database db1’s statements and transactions
  • Replicate the database db2’s statements and transactions
  • Don’t give importance to any transactions or statements that affect other databases
How Replication Functions?

Let’s also see how replication works.

  • Master’s binary log records all the transactions.
  • The slave writes the transactions to its relay log after reading them from the master’s binary log
  • The slave doesn’t start running the statements from its relay log until after that

[Looking for a solution to another query? We are just a click away.]

Conclusion

In this article, We have seen the information provided by our Support team on MariaDB replicate do db. This includes examples and also pointed out the conditions when this filter doesn’t work.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF