Re: replication - queries out of order or dropped?

2003-01-15 Thread David Nedved
Hi Martin,

Replication definitely does not ignore CREATE DATABASE all the time,
just every now and then :)  I had 93 databases that made it through
replication, and the 94th failed.  There aren't any binlog-ignore-db
paramaters.  I've dumped the binlog out, and CREATE DATABASE did make
it into the log, and the slave did make it past that point without
creating the database.

Is there any reason to think that replication is more reliable in
the 4.0 series?

David

On Wed, Jan 15, 2003 at 02:39:34PM +, Martin Waite wrote:
 - sql,query
 
 On Tue, 2003-01-14 at 23:55, Jeremy Zawodny wrote:
  
  What do the relevant sections of the my.cnf files on the master and
  slave look like?
  -- 
 
 Hi,
 
 I've had the same issue - but always assumed that
 replication was meant to ignore create database 
 
 I've looked into it further, and it looks like if
 you have any binlog-ignore-db directives in the 
 master's my.cnf file then create database commands 
 are not routed to the binlog.
 
 ==
 Martin
 
 
 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: replication - queries out of order or dropped?

2003-01-14 Thread David Nedved
I've been doing a lot of poking around...

the actual database is what didn't get created.  The CREATE DATABASE
statement did make it into the log file, and the slave got past that
point without ever creating the database.

Go figure...

On Tue, Jan 14, 2003 at 02:06:39PM -0800, Jeremy Zawodny wrote:
 On Mon, Jan 13, 2003 at 02:16:23PM -0500, David Nedved wrote:
  
  We keep having issues where we create a new table on the master, and
  a short while later the slave will crash because it starts trying to
  perform queries which insert into the new table, but it looks as if the
  query to create the table hasn't been executed yet (ie the table doesn't
  yet exist on the slave).
 
 Use mysqlbinlog to dump the binary log on the master and see if the
 CREATE TABLE statement was logged or not.
 
 Jeremy
 -- 
 Jeremy D. Zawodny |  Perl, Web, MySQL, Linux Magazine, Yahoo!
 [EMAIL PROTECTED]  |  http://jeremy.zawodny.com/
 
 MySQL 3.23.51: up 30 days, processed 1,010,822,567 queries (381/sec. avg)
 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




replication - queries out of order or dropped?

2003-01-13 Thread David Nedved
Hi All,

Trying my best to maintain some production servers running
mysql-max-3.23.53a-pc-linux-gnu-i686 with one master and one slave.

We keep having issues where we create a new table on the master, and
a short while later the slave will crash because it starts trying to
perform queries which insert into the new table, but it looks as if the
query to create the table hasn't been executed yet (ie the table doesn't
yet exist on the slave).

I've got three pairs of master/slave servers, and this is happenning
on all of them.  My experience is that I can brute-force something such
as setting the skip count to some positive integer, etc. etc., but that's
only a hack, and doesn't get around the big problem here which is that
somehow the queries are seemingly getting either skipped or out-of-order.

Any help here?  My management is getting quite upset about this.  We're
not using the slaves for anything at present, but they are meant to be
a disaster recovery option.  Right now they're worthless...

Thanks in advance,

David Nedved

here is the output of show slave status on a currently broken slave:
(sure enough the table exists on the master, but not on the slave)

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 47773 to server version: 3.23.53a-max-log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql show slave status;
+-+-+-+---+--+---+---+-+-+++--+
| Master_Host | Master_User | Master_Port | Connect_retry | Log_File | Pos   | 
|Slave_Running | Replicate_do_db | Replicate_ignore_db | Last_errno | Last_error   
|  
|  
|  
|  
|  | Skip_counter |
+-+-+-+---+--+---+---+-+-+++--+
| 66.83.39.9  | repl| 3306| 60| customer.024 | 146873601 | 
|No| | mysql   | 1  | error 'Can't 
|create/write to file './www_heliumandballoons_com_wa/ACCESS.frm' (Errcode: 2)' on 
|query 'CREATE TABLE ACCESS (
  ID int(1) NOT NULL default '0',
  CATALOG tinyint(1) default NULL,
  DISPLAY_CATALOG tinyint(1) default NULL,
  ECOMMERCE tinyint(1) default NULL,
  DISPLAY_ECOMMERCE tinyint(1) default NULL,
  RESIDENTIAL tinyint(1) default NULL,
  PRIMARY KEY (ID)
) TYPE=MyISAM' | 0|
+-+-+-+---+--+---+---+-+-+++--+
1 row in set (0.00 sec)

mysql 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




binary log questions not in docs...

2002-12-11 Thread David Nedved
Hi All,

I have two qestions about the binary log files that I couldn't find the
answer to.

1.) how do you force a log switch other than startup / shutdown?
2.) when the number gets to 999 does it keep going with more digits, wrap around, or 
some other behavior?

I'm running mysql-max-3.23.53a-pc-linux-gnu-i686 if that matters.

Thanks in advance!

David


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




syntax problem with replicate-rewrite-db

2002-11-19 Thread David Nedved
Hi All,

(sorry if this is a duplicate -- I don't think the original made it)

Running mysql 3.23.53-max binary on a RedHat 7.2 based server.  Replication
is working fine, but I'm running into errors with the replicate-rewrite-db
directive.  Here's a snippet from my my.cnf file on the slave:

master-port = 3306
replicate-rewrite-db=mysql-master_mysql

When I try to start the instance, I get the following error in my
log:

021118 14:30:56  mysqld started
Bad syntax in replicate-rewrite-db - missing '-'!
021118 14:30:56  mysqld ended

I've tried every possible combination of white space I could think of, and 
even cut and pasted the exact syntax from the documentation, and created
tables with those names, yet I still get the same error, so it doesn't appear
to be a problem specifically with replicating the mysql table.

I've also tried mysql 3.23.52-max binary, and gotten the same thing, so
it's definitely not a issue with a specific version of mysql...

Can anyone help figure out how to get this working?  Anyone else using it?

Thanks in advance,

David

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




syntax problem with replicate-rewrite-db

2002-11-18 Thread David Nedved
Hi All,

Running mysql 3.23.52-max binary on a RedHat 7.2 based server.  Replication
is working fine, but I'm running into errors with the replicate-rewrite-db
directive.  Here's a snippet from my my.cnf file on the slave:

master-port = 3306
replicate-rewrite-db=mysql-master_mysql

When I try to start the instance, I get the following error in my
log:

021118 14:30:56  mysqld started
Bad syntax in replicate-rewrite-db - missing '-'!
021118 14:30:56  mysqld ended

I've tried every possible combination of spaces I could think of, and I've
even cut and pasted the exact syntax from the documentation, and created
tables with those names, yet I still get the same error, so it doesn't appear
to be a problem specifically with replicating the mysql table.

Can anyone help figure out how to get this working?

Please copy me directly on any responses, as the list management software
is presently ignoring all my attempts to subscribe.

Thanks in advance,

David

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php