Re: Replication

2003-12-05 Thread rubn ruvalcaba
Stefan:

  Thank you very much, I got the point. I'll make some tests with the 
'log-slave-updates' parameter, I think if the master can log the updates 
made from any slave, then it can propagate the changes to the others.

  Regards


From: Stefan Kuhn [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: rubn ruvalcaba [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Replication
Date: Wed, 3 Dec 2003 18:01:39 +0100
Am Wednesday 03 December 2003 18:21 schrieb rubn ruvalcaba:
 You guys are right, as Cuck said I need each machine acts as server and
 slave, I did it with two servers in a circular replication and works 
pretty
 fine, but when add a third machine, there comes the problems, because 
the
 central server must be the master (no problem) and the slave of two 
servers
 (here is the problem).

If you want to do a circular replication, it needs to be like this:
A is slave of B
B is slave of C
C is slave of A
Important: You need to set log-slave-updates in my.cnf, so that B logs what 
it
gets from C and A gets it then from B.
I have such a configuration in production use and all works fine.
Stefan
P. S: Note your two server configuration is just a special case of this.


 From: Lloyd Kvam [EMAIL PROTECTED]

 To: Chuck Gadd [EMAIL PROTECTED]
 CC: rubn ruvalcaba [EMAIL PROTECTED], [EMAIL PROTECTED]
 Subject: Re: Replication
 Date: Wed, 03 Dec 2003 09:59:29 -0500
 
 You can setup a circular replication stream.  Make sure that the
 replicated data gets written to the output binlogs.  From the
 manual:
 
 `log-slave-updates' Tells the slave to log the updates from the
 slave thread to the binary log. Off by default.
 You will need to turn it on if you plan to
 daisy-chain the slaves.
 
 Chuck Gadd wrote:
 rubn ruvalcaba wrote:
 I want to know how could solve the next replication scenario:
 
 I have a master.
 I have 5 slaves.
 
 At start the slaves has a master snapshot.
 
 Now imagine slave 1, inserts a record. When it gets connected to the
  lan, it must replicate it's changes to the master.
 
 No, a slave receives changes that occur at the master.   That's
 why it's a slave.
 
 I suspect you want each machine to be a Master and a slave.
 
 --
 Lloyd Kvam
 Venix Corp.
 1 Court Street, Suite 378
 Lebanon, NH 03766-1358
 
 voice: 603-653-8139
 fax:   801-459-9582
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/[EMAIL PROTECTED]

 _
 MSN. Más Útil Cada Día  http://www.msn.es/intmap/
--
Stefan Kuhn M. A.
Cologne University BioInformatics Center (http://www.cubic.uni-koeln.de)
Zülpicher Str. 47, 50674 Cologne
Tel: +49(0)221-470-7428   Fax: +49 (0) 221-470-7786
My public PGP key is available at http://pgp.mit.edu
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]

_
Charla con tus amigos en línea mediante MSN Messenger:  
http://messenger.microsoft.com/es

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Replication

2003-12-03 Thread rubn ruvalcaba
You guys are right, as Cuck said I need each machine acts as server and 
slave, I did it with two servers in a circular replication and works pretty 
fine, but when add a third machine, there comes the problems, because the 
central server must be the master (no problem) and the slave of two servers 
(here is the problem).

From: Lloyd Kvam [EMAIL PROTECTED]
To: Chuck Gadd [EMAIL PROTECTED]
CC: rubn ruvalcaba [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Replication
Date: Wed, 03 Dec 2003 09:59:29 -0500
You can setup a circular replication stream.  Make sure that the
replicated data gets written to the output binlogs.  From the
manual:
`log-slave-updates' Tells the slave to log the updates from the
   slave thread to the binary log. Off by default.
   You will need to turn it on if you plan to
   daisy-chain the slaves.
Chuck Gadd wrote:

rubn ruvalcaba wrote:

I want to know how could solve the next replication scenario:

I have a master.
I have 5 slaves.
At start the slaves has a master snapshot.

Now imagine slave 1, inserts a record. When it gets connected to the lan, 
it must replicate it's changes to the master.


No, a slave receives changes that occur at the master.   That's
why it's a slave.
I suspect you want each machine to be a Master and a slave.




--
Lloyd Kvam
Venix Corp.
1 Court Street, Suite 378
Lebanon, NH 03766-1358
voice:  603-653-8139
fax:801-459-9582
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]

_
MSN. Más Útil Cada Día  http://www.msn.es/intmap/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Replication

2003-12-02 Thread rubn ruvalcaba
I want to know how could solve the next replication scenario:

I have a master.
I have 5 slaves.
At start the slaves has a master snapshot.

Now imagine slave 1, inserts a record. When it gets connected to the lan, it 
must replicate it's changes to the master.
Then the slave 2 gets connected to the lan too, and replicate their own 
changes to the master, but it also must receive the changes made on the 
slave 1.

Is it possible to do with mysql replication?

Thanks in advance.

_
Charla con tus amigos en línea mediante MSN Messenger:  
http://messenger.microsoft.com/es

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]