Steve,
your observations suggest that it is MySQL which is holding some
semaphore while it is aborting a connection (which in your case
required a big rollback). The operating system seems to be innocent.
On Windows NT I have seen that disk operations will freeze the
computer almost totally.
Steve,
At 09:48 AM 5/15/01 -0600, you wrote:
Heikki Tuuri wrote:
Steve,
your observations suggest that it is MySQL which is holding some
semaphore while it is aborting a connection (which in your case
required a big rollback). The operating system seems to be innocent.
If the large
There seem to be some operations that cannot be performed on the
server whie InnoDB is doing something.
For example I inserted about 200,000 rows in to a table from
a file (mysql database file) the file starts with begin; and
contains many inserts, I cancelled (ctrl-c) in the middle of the
Heikki Tuuri wrote:
Steve,
on what operating system you are running?
linux, intel 2.2.12
Was the rollback (and the table load) disk bound? Did you configure much
memory to the InnoDB buffer pool?
I would say the rollback was processor bound, the machine was running
with almost no
