Hi, What does exactly happens when the AUTOINC lock is happening ?
Why is it not a problem on our amd (quadcore) machine with the data sitting on a raid10 partition, we have never seen this problem before, its apparently happening so fast that it doesn't matter. With the intel machine (quadcore with hyperthreading enabled) sitting on a DRBD partition (raid 10) the process of getting a lock is slow. So slow, that it cascades to this problem of rollbacks, etc...as show in the previous email. Thanks in advance for your help, Mariella --- Sunny Bains <[EMAIL PROTECTED]> wrote: > Mariella, > > > Mariella Petrini wrote: > > Hi, > > > > > > I have been using 5.0.32 MySQL on Debian. > > Everything worked properly. > > DRBD has been added and configure with MySQL and > > restarted. > > The tables used are InnoDB type and use > > auto_increment. > > > > After that during INSERTs and UPDATEs innodb > started > > to roll back > > for table lock on AUTO_INC > > The behavior observed is most likely related to this > bug report: > > http://bugs.mysql.com/bug.php?id=16979 > > Regards, > -sunny > > Oracle/Innobase. > ____________________________________________________________________________________ Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
