Re: archive engine potential bug

2007-09-11 Thread Rob
also when it hits a dupl. and i skip the record, and continue slave it
hits another duplicate entry almost instantly, when i then drop the
table on the slave, and recreate it manually and set it to myisam at
that time, the slave continues without a problem.


On Tue, 2007-09-11 at 16:42 +0200, WiNK / Rob wrote:
> W00ps forgot to update subject of my email,
> 
> WiNK / Rob wrote:
> > Hi ,
> >
> > I think i might have hit a bug, posted on forums.mysql.com but 
> > apparently nobody really reads that i think.
> >
> > my table:
> >
> > CREATE TABLE `clog` ( `cID` int(20) NOT NULL auto_increment, `lID` 
> > int(10) default NULL, `ip` int(10) default NULL, `timestamp` int(11) 
> > NOT NULL, PRIMARY KEY (`clickID`) ) ENGINE=MYISAM; or i use ARCHIVE
> >
> > I have a bit of a problem that occurs only when i change my really 
> > simple log table to the archive engine. The replication breaks. Any 
> > thoughts? The row number of the error is variable. When the table is 
> > set to myisam, the replication does not break on duplicate key, and 
> > runs as expected.
> >
> > Can't write; duplicate key in table 'clog'' on query.
> >
> > Is it possible that due to the stress of the benchmark, my slave 
> > cannot compute the next cID or creates a duplicate (cId is the only 
> > variable that changes, on bench query)?
> >
> >
> >
> 
> 
> 
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
> 
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


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



archive engine potential bug

2007-09-11 Thread WiNK / Rob

W00ps forgot to update subject of my email,

WiNK / Rob wrote:

Hi ,

I think i might have hit a bug, posted on forums.mysql.com but 
apparently nobody really reads that i think.


my table:

CREATE TABLE `clog` ( `cID` int(20) NOT NULL auto_increment, `lID` 
int(10) default NULL, `ip` int(10) default NULL, `timestamp` int(11) 
NOT NULL, PRIMARY KEY (`clickID`) ) ENGINE=MYISAM; or i use ARCHIVE


I have a bit of a problem that occurs only when i change my really 
simple log table to the archive engine. The replication breaks. Any 
thoughts? The row number of the error is variable. When the table is 
set to myisam, the replication does not break on duplicate key, and 
runs as expected.


Can't write; duplicate key in table 'clog'' on query.

Is it possible that due to the stress of the benchmark, my slave 
cannot compute the next cID or creates a duplicate (cId is the only 
variable that changes, on bench query)?









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