Tag Info

Hot answers tagged

11

KISS Keep it simple silly. I'm kind of lost here. For this very reason, don't begin to overcomplicate something that needs not be complicated. If you don't know the right method to implement something in the first instance - you certainly won't know what to do when something goes wrong. First, lets address the hardware Ref: ...


2

You have to set it up as a ring -- A is the master for B, B is the master for C, and C is the master for A. And don't forget to set the log_slave_updates option so that they will pass on upstream changes, and set replicate-same-server-id to 0 so that the updates won't go round and round the ring for ever. Read this article -- the ring configuration is ...


2

"Telnet" just means you can establish a TCP connection. Don't focus that much on it. The more important information is in your netstat output. As you can see, the MySQL process on Master2 is only listening on 127.0.0.1, not on the "Master 2" interface. You will need to configure MySQL to listen to that interface. On Linux systems, you would edit ...


2

There are two basic approaches to this problem that I am aware of. First, if you are running InnoDB instead of Myisam, then you can do the backup in a transaction (--single-transaction --lock-tables=FALSE), which combined with --flush-logs (not required but nice) and --master-data will give you a consistent backup with replication position information. Flush ...


1

Bucardo only needs to be installed on one host, although obviously, that won't provide HA capability. Typically, in a master-master scenario, it's installed on one of the masters. In the event either of the masters then goes down, the Bucardo daemon wouldn't have anything to do anyway, so HA for it is pretty moot. Some useful links: ...


1

I encountered exactly this problem with a master -> many slave setup. It was even worse than your situation because the reads were guaranteed to come from the slave rather than having a 50/50 chance. Every time a user wrote to the database (such as a forum post or clicking a "like" button) they would get an HTTP redirect to the page that should display ...


1

This depends on your servers performance which is related to how many queries each server has to process, how big are your tables, and so on. Using such replication solution should be synchronous which will definitely imposes some delay during transactions. This is simply because each transaction should not be considered committed completely unless it is ...


1

So, after days of investigation it looks like the answer is 'No' - Mysql replication does not support update conflict resolution options like they are available with Mysql cluster. I just wasn't able to find a single setting or option that would point in the right direction. Unfortunately Mysql Cluster wasn't an option for me because it requires 3 servers ...



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