Hot answers tagged

2

A fast refresh would copy incremental changes over the network but requires that a materialized view log be created on the master site on the source table. That adds some overhead to the inserts happening on the master table but would generally make the refresh more efficient. A complete refresh would copy every row over the network every time the ...


2

In a Galera cluster, any node can play the part of a Master node. Such a node can execute DML (INSERTs, UPDATEs, and DELETEs). If DML statements are spread across multiple Master nodes and are targeting the same tables, you must expect log conflicts. Why ? Galera wsrep libraries were designed to commit DML changes if all nodes in a cluster are ready to do ...


2

You seem to not be connecting to the master that you think you are. Per your binary logs on the master you seem to have: #160519 3:28:59 server id 5 But per SHOW SLAVE STATUS we see: Master_Server_Id: 3 And further you seem to be connecting on localhost, but you implied your master/slave are on different hosts: Master_Host: 127....


1

I wrote this blog post which explains how to create the bash script to automate Master-Slave replication on MySQL: http://blog.ditullio.fr/2016/04/30/initialize-mysql-master-slave-replication-script/ It gives a shell script (see end of the post) where you simply enter in variables: The Master hostname or IP An array of Slave hostnames or IPs The Database ...


1

This information may not be of interest to the DBA. If the application is handling conflicts correctly, there is no need to log them. It would be expected behaviour. You would only enable this level of logging if you were debugging a specific issue. Otherwise it would generate a lot of spam in the logs.


1

Switching a primary in a replica set to a standalone will not impact CPU unless you were offloading something to the secondaries that will now hit the standalone node like reads or Map Reduce (and you mention you were not). As well as that, mongod is generally not CPU intensive unless you are doing lots of sorts or distincts (or a lot of javascript, Map ...


1

Firstly, it doesn’t matter how you configure your replication, the snapshot agent always runs on your distributor. It takes a snapshot of your publication and puts it in snapshot folder, then depends on your replication type, it will be send to subscriber by either distribution agent or merge agent. So publisher doesn’t need access to snapshot folder, ...



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