1

SHOW SLAVE STATUS reports zero seconds behind master (except on slow query updates and so on, when lag is expected). The Seconds_behind_master (aka `Seconds_behind_source on 8.0) only shows the difference between the timestamp of the last binlog entry it has executed on the replica and the timestamp of the last binlog entry it has downloaded. But it doesn't ...


1

Timezone problems? Use TIMESTAMP instead of DATETIME for monitoring. Also compare SHOW VARIABLES LIKE '%zone%' between the servers. Transactions are sent to the Replicas immediately after COMMIT. Check that you either run with autocommit=ON or explicitly use COMMIT. (There is no megabyte threshold.) Backups using mysqldump (or similar tool) can clog ...


1

Follow the documentation for define a column filter https://docs.microsoft.com/en-us/sql/relational-databases/replication/publish/define-and-modify-a-column-filter?view=sql-server-ver15


1

re-creating the triggers after I run the snap does the trick for me. The way I do it and it has always been worked is the following: Before I run the snapshot and reinitialize the subscriptions, I go to the subscription databases and script out all the permissions, triggers, synonyms, and in some cases the indexes (when indexes in the subscription are ...


1

The binary log contains changes to data or metadata. I.e., INSERT/UPDATE/DELETE/REPLACE, and also CREATE/ALTER/DROP/TRUNCATE statements. It isn't necessarily due to malicious traffic. It could simply be creating records of users visiting your site, or making copies of versions of wordpress posts as you edit them. You can use mysqlbinlog to inspect the binary ...


1

"are in the same server as virtual machines" -- This means that they are competing for CPU and I/O, especially during the backup. Is this just a test? I would not deploy Galera with all nodes on a single machine. When SST is involved, 2 of the 3 nodes are involved. The donor is busy fetching and sending data; the recipient cannot receive ...


1

Alternatively to MBuschi's great idea, you can also look into possibly using an INSTEAD OF INSERT trigger on the DeviceData table. This trigger would first verify the data you need is in the Device table, and then would insert the replicated data into your DeviceData table. (Here's Microsoft's Books Online for Triggers.) One pro of this solution is it doesn'...


Only top voted, non community-wiki answers of a minimum length are eligible