Tag Info

Hot answers tagged

5

You can create secondary indexes on slave whenever required. There is no issue in creating secondary indexes (Non Primary and Non Unique). If you create Primary and Unique on slave there will be chances that your replication will fail with duplicate key error on slave. Take a example I have a table testRepl on master without having any index on it and has ...


5

This is due to MySQL Master and Slave version mismatch The message below is clear, and confirms the master/slaves run different versions. The variable SERVER_UUID is not supported with MySQL 5.5 but is supported with MySQL 5.6 2015-06-29 11:01:01 8026 [Warning] Slave I/O: Unknown system variable 'SERVER_UUID' on master. A probable cause is that the ...


1

Know this is an old question but we've just been working with this, Last month we had to move our distribution server to a brand new machine, (Setup is two machines in AG stand alone distributor and a reporting server) The only real way we found to move distributor server is to completely tear down and rebuild replication, this can be done with right ...


1

You can use Transaction Replication, if you can fulfill its considerations regarding: Transaction log space. Disk space for the distribution database. Primary keys for each published table. Triggers. Large object (LOB) data types. Transaction Replication allows data modified at Publisher to be delivered to the Subscriber as they occur (in near real ...


1

Hopefully, you did not start mysqld on the slave yet. It just so happens that a binlog position is also the binlog size at the end of every binlog event. In your case, you can use the last binlog the slave sees, which I can assume is mysql-bin.000006. Get the filesize and use that as the position. Therefore, on the Slave you would run STOP SLAVE; CHANGE ...


1

Reason: Is it the same version of Mongo on both servers? Record Padding : http://docs.mongodb.org/v2.4/core/record-padding/ No Padding Allocation Strategy Changed in version 3.0.0. For collections whose workloads do not change the document sizes, such as workloads that consist of insert-only operations or update operations that do not increase document ...


1

Nick, based on the information we've gathered, I'm going to venture a guess, but if I'm wrong, come back and let us know and there may still be something we can do. I wouldn't say I'm confident about the internals of auto-vacuum processes on hot standby servers. Streaming Replication, aka Log-Shipping Streaming replication, hot standby, log ...


1

You will probably need to enable log_slave_updates so the slave node generates binlog to be used on other nodes. http://www.severalnines.com/blog/replicate-mysql-server-galera-cluster


1

In MySQL 5.6, mysqldump can do that for you with --dump-slave=1 and --single-transaction. It is the same as --master-data=1, but here is how the log file and position are retrieved: --master-data=1: log file and position from SHOW MASTER STATUS; --dump-slave=1: Relay_Master_Log_File,Exec_Master_Log_Pos from SHOW SLAVE STATUS\G. --dump-slave=1 will run do ...


1

If you want to setup slave from another slave steps would be as follows Flush tables with read lock to lock the slave so it should not get updates show slave status\G and note master co-ordinates Take backup now using mysqldump unlock tables to unlock the slave transfer that backup and restore it to new one Hope you have issues grant replication slave on ...


1

Change the default_master_connection variable for the session to make it work for a specific multi-source connection: STOP SLAVE 'src1'; SET @@default_master_connection = 'src1'; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; START SLAVE 'src1'; SET @@default_master_connection = '';


1

The intent of replication is that the dataset on the Slave is always identical to what is on the Master. But, Stored Procedures, Stored Functions, Triggers, and Events may (or may not) do things that should not be re-done on the slave. Therefore, you must decide case by case whether you want them to be on both servers. To apply a CREATE to all your slaves ...


1

We have few replications in my shop and anytime we stop a master, prior to doing so we stop replication on the slave with: STOP SLAVE;


1

Could you give us some info on the replication config in your config files. For sure if you replicate one db at a time and you need to add one, you won't have a choice to change your config then to restart your instances. If you can I'll suggest more a full replication. less trouble and if you need to add dbs, there is no problem there.


1

I try to answer below, but: DON'T DO THIS! You are planning a disaster recovery setup, but when the disaster hits the shared storage (the SAN), you will stand there with no usable database. You can do that, yes, just as @a_horse_with_no_name describes in his comment. You have to have two separate data directories for it, the master pointing to one and ...


1

Using the topology you mentioned from the MySQL Documentation Let's setup the first scenario EXAMPLE IPs for Each DB Server Master1 : 10.20.30.40 Master2 : 10.20.30.50 Slave_1 : 10.20.30.60 replication user is repluser@'%' replication password is replpass Make sure binary logging is enabled on all the Slaves We will do the following Promote ...


1

Neo4j is a master-slave cluster. While you can write to slaves for safety, it will take locks on the master and affect your whole cluster's performance.



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