Heikki,
After a good 6-8 hours of runnning, the server just restarted itself
(running the most recent build from the 3.23.xx tree, as you
suggested). I got this message:
InnoDB: Assertion failure in thread 42527756 in file ha_innobase.cc
line 316
InnoDB: We intentionally generate a memory
On Wed, May 29, 2002 at 12:13:49AM -0700, Jeremy Zawodny wrote:
Heikki,
After a good 6-8 hours of runnning, the server just restarted itself
(running the most recent build from the 3.23.xx tree, as you
suggested).
Just for the record, it happened again. So it's reproducable to a
dregree.
-transaction.all.innobase_tid = NULL;
}
return(0);
}
- Original Message -
From: Jeremy Zawodny [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, May 29, 2002 10:13 AM
Subject: InnoDB crash repeated under 3.23.51...
Heikki
Subject: InnoDB crash repeated under 3.23.51...
Heikki,
After a good 6-8 hours of runnning, the server just restarted itself
(running the most recent build from the 3.23.xx tree, as you
suggested). I got this message:
InnoDB: Assertion failure in thread 42527756 in file ha_innobase.cc
On Wed, May 29, 2002 at 02:06:19PM +0300, Heikki Tuuri wrote:
Jeremy,
it looks like this crash can happen if you use MySQL 'user level locks'
which are kind of semaphores. In that case MySQL will write a binlog entry
even after THD::cleanup where the transaction handle is freed.
From the
