New answers tagged

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

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 ...


0

The exact reason of why this happens, is because SESSION variables are replicated explicitly in the binary log. Here is an example of an entry header in the binary log: # at 368008153 #160624 9:15:24 server id xxxxx end_log_pos 368008235 Query thread_id=1097746 exec_time=0 error_code=0 SET TIMESTAMP=1466774124/*!*/; SET @@session.pseudo_thread_id=...


0

You should also check that these two lines are commented on the Master side (for networking issues) as shown below. # skip-networking # bind-address = 127.0.0.1 For complete details on master slave replication, follow this link.


0

So after a lot of struggle and a lot of load testing, we solved the problem by upgrading PyMongo to 2.8.1. PyMongo 2.7.2 is the first version to support MongoDB 2.6 and it sure does have some problems handling connections. Upgrading to PyMongo 2.8.1 helped us resolve the issue. With the same load, the connections do not exceed 250-300.


-1

create replication user on backup configure replication on live as slave and backup as master start slave profit!


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 ...


0

The idea of semi-synchronous is to wait for acknowledgement from at least one slave and since you would be using master-master so you might have to install both plugins i.e. for master & slave on both nodes. This is because when one master would write the other would behave like it's slave and same goes for the other case. Hope it helps


0

So after fiddling more, I've discovered the order of CHANGE MASTER ... is important. Once I figured this out, I found this in the docs explaining in further detail. If you specify the MASTER_HOST or MASTER_PORT option, the slave assumes that the master server is different from before (even if the option value is the same as its current value.) In this ...


0

What OGG version are you using? Instead of DBA role, have you tried granting the required privileges through dbms_goldengate_auth.grant_admin_privilege? "Requirements When Configuring Extract or Replicat in Integrated Mode (Oracle) If using DBLOGIN to issue ADD EXTRACT, ALTER EXTRACT, or REGISTER EXTRACT to initiate integrated capture or ADD REPLICAT, ...


0

Having mongo as a replica set allows for: (this things will be unavailable in single instance) Overcome failure of a master system (with low latency) have data distributed (in two/three different data centres) Split load and allow to query secondaries Overcome network segmentation issues When you switch to one instance - whatever will stop the only ...


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 ...


0

To counter such issues in production environment, where consistency of data is priority, if slave servers are being actively used for read purpose by applications, it's a best practice to deploy an automated discrepancy check and sync script (as a daily cron) between master and slave server using pt-table-sync (available with Percona toolkit). I have tested ...


0

Duplicate Database It is separate database contains all or subset of the data of Source Database. Its purpose varies like: Test backup/recovery procedure Test upgrade of new release Test effect of DB performance Generate reports Export data table and import in production environment if inadvertently dropped Snapshot Replication Here data is replicated ...


0

I faced a similar error some days ago. I was able to solve that error based on some Google search results. Here are some of the suggestions that might hopefully help you too: Check whether you created the replication user with required privileges. If not, create a new user on master with the following command: Create user ‘repl’@’192.168.2.46’ identified ...


0

It's fine to write to the master directly. A database does much more for you than just persist your changes to disk. It manages transaction, enforces integrity, etc. If you introduce a queue you introduce a new cog in the machine that can break and a lot of complexity that you need to manage for yourself and that is actually not required in most cases. I ...


0

An alternative would to remove the article from the publication and re add, causing a new snapshot to be taken of the table. This way there's no question whether the right data is in the subscriber. To do this you need to make sure the publication properties are set to FALSE for allow_anonymous and immediate_sync - if either of these are true then the a ...


0

I had this same issue, and found out that I simply had the name of the replica set wrong in the addShard command.


0

----- 2014-09-25 5.7.5 Milestone 15 -- Functionality Added or Changed -- Replication ----- When replicating from a master running a version earlier than MySQL 5.6.0 to a slave running MySQL 5.6.0 or later, the slave requires the master_uuid value, which is the server_uuid ( http://dev.mysql.com/doc/refman/5.7/en/replication-options.html#sysvar_server_uuid ) ...


0

As it turns out, the problem was that we were connecting to an old (wrong) master. The previous master was domain.com, but many months ago, we migrated to db.domain.com. It seems that we were erroneously connecting to domain.com. We’re using autossh to set up SSH tunnels for our replication. To confirm that we were connecting to the old (wrong) master, I ...


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....


0

Since you have binlog/replicate filtering, this is probably what happened: USE non_replicated_db; CREATE TABLE replicated_db.table_name ...; The filtering works on the USE, not on the db qualification in the statement. (PS, you are using what is probably the best layout for standard replication: dual-master-single-writer, plus slaves hanging off both. ...


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, ...


3

While MySQL does not impose a password length limit, replication does. (I have not been able to find this in the MySQL documentation, but, empirically, it holds.) This is all the less obvious, because the longer password works for login but fails for replication. So, in the end, reducing the password to 32 characters solved the problem.



Top 50 recent answers are included