Tag Info

Hot answers tagged

3

Yes, you are correct. This relies on the server ID being set correctly in the standard MySQL configuration. In MySQL 5.6 and above you can configure the server to use GTIDs (Global Transaction IDentifiers) and they are used on all servers to determine if transactions need to be executed or not


3

You could setup a script to read the binary log, convert it to SQL (with the utility mysqlbinlog) and change the schema on-the-fly before applying the changes. You could also setup triggers on every table to INSERT/UPDATE/DELETE every row on the copy schema. But that is a lot of work to do it right. Running 2 instances of MySQL on the same machine is very ...


2

To initialize a Transactional subscription from a backup you actually end up creating the publication first, enabling it to initialize subscriptions from a backup, then take a backup, and then initialize subscriptions with the backup. Changes that occur after taking the backup and before initializing the subscription(s) will be stored in the distribution ...


2

Does the same data take more storage space in version 2.6? As noted in the MongoDB 2.6 release notes, the default storage allocation strategy changed from using exact-fit allocation with padding factor to usePowerOfTwoSizes. The powerOfTwoSizes allocation may take up more initial space, but generally results in less storage fragmentation and better reuse of ...


2

Please help me on how can i find for what could have been possibly going wrong where data does not match between both the DB. You can use tablediff utility to find out the difference in data between your Publisher and Subscriber server. Check How to run TableDiff utility for ALL replicated tables ? article by Chris Skorlinski on REPLTalk. This blog has ...


2

I assume GTID has been already enabled on the master: Stop the master server Copy your data directory to the slave host Start the master. Technically it is not needed, but if you do not feel safe with what you do and want to be 100% sure everything is correct before continuing with replication- you can start it in read-only mode. Once you see that it is ...


2

OBSERVATION #1 The slave needs log-slave-updates in my.ini OBSERVATION #2 Both Master and Slave need binlog_gtid_simple_recovery in my.ini MySQL Restart is required on both Master and Slave to include new options SUGGESTION Since DB is 5GB, just mysqldump the database on the Master. No need for raw copying STEP 01 : On the Master, run this RESET ...


1

As mentioned, the slave is set up to do two way replication, and there was actually some advice in the error log: these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense In this case, adding replicate-same-server-id = 1 to the slave my.cfg worked and may be all ...


1

You didn't setup the server-id variable, or you didn't restart after doing it (it is not a dynamic variable, changes will not be effective until you restart). It may be showing you a good id on both servers, but it will not really work until both servers are restarted, both master and slave. It could be a bug, but the above has happened too many times on ...


1

When doing this: $ psql -h $MASTER_PORT_5432_TCP_ADDR -U replication psql: FATAL: no pg_hba.conf entry for host "$SLAVE_PORT_5432_TCP_ADDR", user "replication", database "replication", SSL off Since there's no explicit database indicated with -d (for example -d postgres ), it takes replication as the database, the same as the user name. However that's ...


1

Regarding de-synchronization of a single or master server: Mosty, the cause of these problems come from the fact that the master is not in full ACID mode or it is using MyISAM tables. In order to avoid problems with a server, only use InnoDB as the engine of your tables and set innodb_flush_log_at_trx commit to 1. This is not efficient -you will lose a lot ...


1

Please keep in mind what MySQL Documentation says on sync_binlog: If the value of this variable is greater than 0, the MySQL server synchronizes its binary log to disk (using fdatasync()) after sync_binlog commit groups are written to the binary log. The default value of sync_binlog is 0, which does no synchronizing to diskā€”in this case, the server ...


1

You are likely using the Express Edition. Note that Express Edition can only act as a Subscriber. Try using Standard Edition or above to Configure Distribution and Publishing.


1

I would say your basic process is quite straight forward. 1) Ensure that slave1 has got log-bin and log-slave-updates enabled (this will require a restart if not) 2) Take a copy of Slave1 and set up Slave2 as a slave of Slave1. You now have Master -> Slave1 -> Slave2 3) Once you are happy that Slave2 is performing as expected, set GLOBAL ...


1

This currently isn't practical. Writes may not be done on a downstream replica, whether it replays WAL via streaming or archives. However, the logical decoding feature in PostgreSQL 9.4 sets the foundations for making this sort of thing possible. You could have a logical decoding plugin that reads the change-stream from the master server, then writes audit ...


1

You have 5 servers serv1,serv2,serv3,serv4,serv5 and you want to set up 5 instanses inst1,inst2,inst3,inst4,inst5. Each instance should have at least 2 data nodes (PRIMARY and SECONDARY) and 1 ARBITER serv1: inst1_PRI, inst5_SEC, inst4_ARB serv2: inst2_PRI, inst1_SEC, inst5_ARB serv3: inst3_PRI, inst2_SEC, inst1_ARB serv4: inst4_PRI, inst3_SEC, inst2_ARB ...


1

I have personally had experience with Transactional Replication. In my case, I configured the Distributor at the Report Server, and then created the Publication on Live server to be controlled from the Report Server. The Subscription from the Report Server worked perfectly. With this configuration, I was successfully able to replicate data from the Live ...


1

DISCLAIMER : Not a Neo4j expert IMHO I would yes because the architecture link you gave sounds a lot like Percona XtraDB Cluster. The underlying replication scheme is driven by Galera. In essence, all nodes check with one another before doing transaction commits or rollbacks. This also means that you can run inserts, updates, and deletes on any node in ...


1

The Snapshot Agent process account used to connect to the Distributor must be db_owner in the distribution database and have read, write, and modify permissions on the snapshot share. The account used to connect to the Publisher must be db_owner in the publication database. The Log Reader Agent process account used to connect to the Distributor must be ...



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