Comments on: MySQL: How do you set up master-slave replication in MySQL? (CentOS, RHEL, Fedora)

By: anoopl

anoopl — Thu, 11 Mar 2010 21:21:09 +0000

Hi,

Thanks Man…..
You saved me!
_^_
AnoopL

By: HyperDB Explained Part 2 « life by way of media

HyperDB Explained Part 2 « life by way of media — Fri, 08 May 2009 21:07:15 +0000

[...] Crazytoon – Another article that I referenced [...]

By: imsoft

imsoft — Sun, 10 Aug 2008 09:26:53 +0000

[quote]
Hi,

I was wondering if the following scenario would be possible.

Server 1: Database X (master)
Server 2: Database Y (master)

- replicating to -

Server 3: Database X, Database Y (slave)

The databases are independent, each master:slave relationship is still 1:1. However, as the slave server only seems to accept configuration details for one master server I can’t figure out if this is possible.

Does anyone have any experience of this?
[/quote]

Maybe the following is one of the solutions.
http://www.ziddu.com/download/1886062/mm-single-slave-repl.pdf.html

By: Sunny Walia

Sunny Walia — Wed, 16 Jul 2008 16:35:50 +0000

Chris it’s caused by this: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work

So in your my.cnf on either master or slave, change the: server-id = # <- to another number.

Let me know if it works or not.

By: Chris Chandler

Chris Chandler — Wed, 16 Jul 2008 15:03:32 +0000

Slave Replication Errors. Can you tell me what is wrong?

[root@dhi015 mysql]# tail mysql.err
080716 8:24:30 InnoDB: Started; log sequence number 0 43665
080716 8:24:30 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.0.45-log’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 Source distribution
080716 10:57:05 [Note] Slave SQL thread initialized, starting replication in log ‘FIRST’ at position 0, relay log ‘/var/log/mysql/mysql-relay-bin.000001′ position: 4
080716 10:57:05 [Note] Slave I/O thread: connected to master ‘dhi16_slave@10.10.10.15:3306′, replication started in log ‘FIRST’ at position 4
080716 10:57:05 [ERROR] The slave I/O thread stops because master and slave have equal MySQL server ids; 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; please check the manual before using it).
080716 10:57:05 [Note] Slave I/O thread exiting, read up to log ‘FIRST’, position 4
[root@dhi015 mysql]#

Thanks – Chris

By: claudia

claudia — Fri, 23 May 2008 12:44:39 +0000

I would like to know in case that the master does not respond and if for that reason i want to use the slave as the master (until the original master server is alive again) what steps should i do for allowing this

By: MySQL Replication Series: How does MySQL replication works? | Technology: Learn and Share

Thu, 17 Apr 2008 16:36:30 +0000

[...] You can learn setting up two type of replication MySQL offers here: master-master replication and master-slave replication. Once you have replication set up, you can start playing with it without doing any more changes to [...]

By: Sunny Walia

Sunny Walia — Mon, 14 Apr 2008 06:54:52 +0000

Electron,

You can run 2 instances on server 3 to accomplish this.

By: Elektron

Elektron — Sun, 13 Apr 2008 22:46:05 +0000

Hi,

I was wondering if the following scenario would be possible.

Server 1: Database X (master)
Server 2: Database Y (master)

- replicating to -

Server 3: Database X, Database Y (slave)

Does anyone have any experience of this?

By: Norberto

Norberto — Fri, 11 Apr 2008 14:37:01 +0000

Hello. Is it possible to replicate using mysql server version 3.x as master and mysql server version 5 as a replication host? Thanks in advance. Norberto

By: Bestie

Bestie — Wed, 09 Apr 2008 16:15:53 +0000

Looks like my.ini is a Windows specific (probably why I didn’t know about it) thing from the link below it looks like on windows mysql will accept configuration options from either a my.ini or a my.cnf (neither MUST exist) and they may be located in a number of places with different effects, either global or user specific.

From a brief read of the page it seems like there is no difference between a my.ini or a my.cnf and the same options can be placed in both including the one I mentioned previously.

I have in my ‘my.cnf’:
innodb_table_locks = 0

http://dev.mysql.com/doc/refman/5.0/en/option-files.html

Also there are loads more fun InnoDB options to play with here:

http://dev.mysql.com/doc/refman/4.1/en/innodb-parameters.html

By: ultrabill

ultrabill — Tue, 08 Apr 2008 13:08:54 +0000

homebrew > this method is ok.

I used it with two servers : master on linux, slave on windows 2K3

With my.ini, be carreful about the paths. I.e.:
relay-log = “X:/mysql/mysql-relay-bin”

Yes, use slashes like Unix (not backslashes as usual with windows) ans put your path under quotes.

By: homebrew

homebrew — Mon, 07 Apr 2008 20:18:25 +0000

I don’t have a MY.CNF I have a MY.INI though and it looks like that’s the place to edit ??
I’ve seen various instructions about editing these files, and they’re all different !! So I can’t figure out what’s right.

By: Bestie

Bestie — Fri, 04 Apr 2008 08:51:54 +0000

if table locks are a problem try converting your tables from MyISAM to InnoDB and and set innodb_table_locks off in your my.cnf if you don’t have access to that I think you can change the setting with SET GLOBAL innodb_table_locks OFF.

one of the superior features of InnoDB is that it can do row level locking rather than the table level.

By: Sunny Walia

Sunny Walia — Fri, 28 Mar 2008 05:26:26 +0000

Yes. Just follow the same thing you use to setup first slave to setup n numbers of slaves. Just keep incrementing the id.

By: Robert

Robert — Mon, 24 Mar 2008 22:57:18 +0000

I wish to have two slaves. Is this possible by using the same config but with “server-id = 3″?

By: Michal

Michal — Wed, 05 Mar 2008 09:54:41 +0000

Hi, i set last day the master/slave replication – it works! The next step – i would like to replicate different DBs from more masters to one slave. Is it possible?

By: MySQL: How do you set up master/master replication in MySQL? (CentOS, RHEL, Fedora) | Technology: Learn and Share

Fri, 29 Feb 2008 21:30:10 +0000

[...] document.write(“”); } )() Setting up master/master replication in MySQL is very similar to how we set up master/slave replication. You can read up about how to setup master/slave replication in my previous post: How to set up [...]

By: Andrew

Andrew — Tue, 05 Feb 2008 15:16:57 +0000

I have a lot more to learn, interesting.

By: CrazyToon

CrazyToon — Mon, 04 Feb 2008 22:24:30 +0000

You would do that in code. Just remember that after you do insert, it might take a sec or two to show up on slave. Best thing to do is to do a insert, and leave user on master for a while. Amount of time you leave user on master depends on what kind of setup you have ie. using innodb vs myisam, how many inserts are happening, etc.

By: Andrew

Andrew — Mon, 04 Feb 2008 04:22:59 +0000

nice entry, was wondering if you can answer this question. you mentioned that doing master/slave replication, you can have insert in master, and select in slave. does it do that automatically by following your tutorial or these’s something else needs to be done? and can i tell which goes to which?

By: HC

HC — Fri, 01 Feb 2008 22:38:55 +0000

Thanks. Will give it a try. I would be very helpful if you could also explain what the configuration options mean/do.
Regards,
HC