Re: innodb rollback 30x slower than commit normal?

2009-05-09 Thread Simon J Mudd
nik...@doppelganger.com (Nikita Tovstoles) writes: We have a java-based webapp that talks to MySQL 5.1 INNODB in READ_COMMITTED. We use Hibernate and optimistic concurrency, so periodically concurrent write attempts cause app-level Exceptions that trigger rollbacks (and then we retry tx).

innodb rollback 30x slower than commit normal?

2009-05-07 Thread Nikita Tovstoles
We have a java-based webapp that talks to MySQL 5.1 INNODB in READ_COMMITTED. We use Hibernate and optimistic concurrency, so periodically concurrent write attempts cause app-level Exceptions that trigger rollbacks (and then we retry tx). We've added app-level caching and turned down our tomcat

Re: innodb rollback question

2007-11-19 Thread B. Keith Murphy
. - Original Message From: B. Keith Murphy [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Friday, November 16, 2007 10:29:17 AM Subject: innodb rollback question I have something to throw out. I just got done importing 140 million rows from a myisam table to a innodb table. While it worked I had

Re: innodb rollback question

2007-11-18 Thread mos
At 02:05 PM 11/16/2007, you wrote: How do you import the data? Load data from file is faster thought so better to export myisam - file and then you do load data from file make sure you set autocommit=0 to make it faster Ady, Sure but won't the entire Load Data will still be wrapped in a

innodb rollback question

2007-11-16 Thread B. Keith Murphy
I have something to throw out. I just got done importing 140 million rows from a myisam table to a innodb table. While it worked I had a thought about 3/4ths of the way through. What if the transaction had been canceled about 130 million rows in? It would have taken weeks to roll back.

Re: innodb rollback question

2007-11-16 Thread William Newton
: B. Keith Murphy [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Friday, November 16, 2007 10:29:17 AM Subject: innodb rollback question I have something to throw out. I just got done importing 140 million rows from a myisam table to a innodb table. While it worked I had a thought about 3

Re: innodb rollback question

2007-11-16 Thread Ady Wicaksono
How do you import the data? Load data from file is faster thought so better to export myisam - file and then you do load data from file make sure you set autocommit=0 to make it faster On Nov 17, 2007 12:29 AM, B. Keith Murphy [EMAIL PROTECTED] wrote: I have something to throw out. I just

Re: InnoDB Rollback - 162 hrs remaining!?

2005-02-27 Thread Heikki Tuuri
] Newsgroups: mailing.database.myodbc Sent: Sunday, February 27, 2005 12:33 AM Subject: Re: InnoDB Rollback - 162 hrs remaining!? John, - Original Message - From: John Taylor [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Saturday, February 26, 2005 11:37 PM Subject: Re: InnoDB

InnoDB Rollback - 162 hrs remaining!?

2005-02-26 Thread John Taylor
Hi, We have a large InnoDB table to which we recently added an index. That index creation thread was issued a kill yesterday due to length of time, unfortunately according to 'show innodb status' the rollback is now 162 hrs away from completion (1 every 5 secs). We are not using per-table

Re: InnoDB Rollback - 162 hrs remaining!?

2005-02-26 Thread Heikki Tuuri
John, - Original Message - From: John Taylor [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Saturday, February 26, 2005 6:54 PM Subject: InnoDB Rollback - 162 hrs remaining!? Hi, We have a large InnoDB table to which we recently added an index. That index creation thread

Re: InnoDB Rollback - 162 hrs remaining!?

2005-02-26 Thread John Taylor
: mailing.database.myodbc Sent: Saturday, February 26, 2005 6:54 PM Subject: InnoDB Rollback - 162 hrs remaining!? Hi, We have a large InnoDB table to which we recently added an index. That index creation thread was issued a kill yesterday due to length of time, unfortunately according

Re: InnoDB Rollback - 162 hrs remaining!?

2005-02-26 Thread Heikki Tuuri
John, - Original Message - From: John Taylor [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Saturday, February 26, 2005 11:37 PM Subject: Re: InnoDB Rollback - 162 hrs remaining!? Thanks for the quick response. I note within the database directory a #sql- file but it has

InnoDB rollback

2004-02-02 Thread Keith Thompson
I just had a script fail unexpectedly and now I've got a couple hundred thousand undo entries rolling back. Yes, I realize that I should be committing smaller groups--my bad. I was really hoping to restart my server tonight to change some server parameters, but a rollback like this will take

Re: Do InnoDB rollback segments expand dynamically?

2003-09-09 Thread Heikki Tuuri
Bill, - Original Message - From: Bill Todd [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, September 09, 2003 4:27 AM Subject: Do InnoDB rollback segments expand dynamically? Using InnoDB with an autoextend tablespace, if I start a transaction that results

RE: Do InnoDB rollback segments expand dynamically?

2003-09-09 Thread Bill Todd
: Heikki Tuuri [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 10:44 PM To: [EMAIL PROTECTED] Subject: Re: Do InnoDB rollback segments expand dynamically? Bill, - Original Message - From: Bill Todd [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday

Re: Do InnoDB rollback segments expand dynamically?

2003-09-09 Thread mos
At 12:43 AM 9/9/2003, you wrote: Bill, - Original Message - From: Bill Todd [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, September 09, 2003 4:27 AM Subject: Do InnoDB rollback segments expand dynamically? Using InnoDB with an autoextend tablespace, if I start

Do InnoDB rollback segments expand dynamically?

2003-09-08 Thread Bill Todd
Using InnoDB with an autoextend tablespace, if I start a transaction that results in many record versions, will the rollback segments grow dynamically and force the tablespace to grow dynamically to provide the required room for record versions in the rollback segments? Bill -- MySQL General