Bgs a écrit :
>
> Greetings,
>
> We have regular problems with mysql replication when there is a db
> change. This is mostly ALTER TABLE. The sync breaks and we either have
> to do the changes manually or either shut down the whole system for a
> new sync from zero. Is there a way to sync alter
Greetings,
We have regular problems with mysql replication when there is a db
change. This is mostly ALTER TABLE. The sync breaks and we either have
to do the changes manually or either shut down the whole system for a
new sync from zero. Is there a way to sync alter table commands on the
f
[EMAIL PROTECTED] wrote:
So this would imply that you cannot simply stop/start a slave server -
instead, I would need to write a wrapper script that stops the slave
using "STOP SLAVE", and at next startup, read the master.info file to
find out where it left off, and then issue a "CHANGE MASTER TO..
ave. Which MySQL version or release on what O/S?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 9:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Problems with replication restarting
So this would imply that you cannot simply stop/start a sl
42
To: Round, Mark - CALM Technical <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Problems with replication restarting
[EMAIL PROTECTED] wrote:
>However, when I restart the slave (through init scripts, or when
>rebooting the server etc.), instead of continuing on from where i
[EMAIL PROTECTED] wrote:
However, when I restart the slave (through init scripts, or when
rebooting the server etc.), instead of continuing on from where it left
off, it appears to start again from the beginning. This is confirmed by
watching the value of Relay_Log_Pos from SHOW SLAVE STATUS\G.
Hi all,
I originally posted this to the replication list, but as I haven't yet
received a response, I thought I'd try my luck here...
I'm having some troubles with replication, in particular restarting a
slave. I'm using MySQL 4.0.22 for the slave, and 4.0.21 as the master.
I've followed the inst
Neil Gunton wrote:
>
> Since I didn't get any replies to my previous message (see below), I am
> trying to compile MySQL myself, to see if it results in a more stable
> system when using replication. However this is failing consistently with
> the following error:
>
> make[4]: Entering directory
Since I didn't get any replies to my previous message (see below), I am
trying to compile MySQL myself, to see if it results in a more stable
system when using replication. However this is failing consistently with
the following error:
make[4]: Entering directory `/usr/src/mysql-4.0.17/sql'
source
I am using 4.0.17 rpm on Red Hat 7.3 (fully updated). I have a server
colocated at my local ISP, and my workstation is on ADSL behind a Netsys
router (the ADSL ISP uses PPPoE, don't know if that's relevant or not).
The server has RAID 1, and has always been 100% reliable (up since
2000). I have bee
Hi,
I've got a replication setup with 3.23.51 on two boxes running Mac OS X.
For some reason, ALTER TABLE statements, and DELETE FROM TABLE
statements (with no where or limit clause), don't seem to be replicated
to the slave.
Has anyone else experienced problems like this?
sql,query
--
Gabri
>Description:
Hi!
My name is Ales Perme. A college of mine Samo Login gave me this adress, which was
given to him by Monty, to report MySQL bugs to. The first bug report today from me is
connected with replication.
Our production comprizes of Windows and Linux machines. MySQL verson we are usi
Guilhem,
this is a known problem and mentioned in the Restrictions section of the
InnoDB online manual.
It is not the correct way to run SQL statements in the autocommit mode on
the slave server, while the master has normal transaction processing on.
I have asked Sasha to add COMMIT marks to th
Guilhem,
this is a known problem and mentioned in the Restrictions section of the
InnoDB online manual.
It is not the correct way to run SQL statements in the autocommit mode on
the slave server, while the master has normal transaction processing on.
I have asked Sasha to add COMMIT marks to th
Hi!
> "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes:
Heikki> Guilhem,
Heikki> this is a known problem and mentioned in the Restrictions section of the
Heikki> InnoDB online manual.
Heikki> It is not the correct way to run SQL statements in the autocommit mode on
Heikki> the slave ser
Hi!
> "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes:
Heikki> Guilhem,
Heikki> this is a known problem and mentioned in the Restrictions section of the
Heikki> InnoDB online manual.
Heikki> It is not the correct way to run SQL statements in the autocommit mode on
Heikki> the slave ser
Guilhem,
this is a known problem and mentioned in the Restrictions section of the
InnoDB online manual.
It is not the correct way to run SQL statements in the autocommit mode on
the slave server, while the master has normal transaction processing on.
I have asked Sasha to add COMMIT marks to th
Hello there,
I use MySQL (4.0.1) with InnoDB tables with binary logging on.
I see that the
BEGIN and COMMIT statements that wrap my queries are
not written to the binary log. I perfectly understand this if
I have one server. But assume I have a master server, and a
slave server that replicates
Hello everybody,
I have problems with replication from master to slave over ssh-tunnel.
The port-forwarding is realized with command :
ssh -N -f -L 23306:master:3306 localhost
on the slave.
After starting mysql I've got error-messages:
011220 14:57:00 mysqld started
/usr/sbin/m
this is very urgent:
The slave returns this on the error log;
010208 12:06:58 Slave thread: error connecting to master:Can't connect
to MySQL server on '0' (111)(107), retry in 200 sec
What's '0'? I've configured an IP to that.
--
Leonardo Dias
Catho Online
WebDeveloper
http://www.catho.co
To: [EMAIL PROTECTED]
Subject: Problems with Replication
The problem I'd like to report is when there's an insert with now() in a
datetime field.
The problem is that, when both servers doesn't have their clocks
synchronized, the value of the now() in the Master will be different
from
The problem I'd like to report is when there's an insert with now() in a
datetime field.
The problem is that, when both servers doesn't have their clocks
synchronized, the value of the now() in the Master will be different
from that in the Slave.
I've tried it with MySQL 3.23.32 in both servers.
22 matches
Mail list logo
