Did you run out of disk space? If not what transaction model are you using? Is it repeatable read? If so, are you allowing the transaction to finish with a commit? If not your filling your transaction log and that's how your getting this message. Call commit on the session OR SET AUTOCOMMIT=1 on connection. Additionally set your innodb_deadlock_timeout var.
-- DVP > -----Original Message----- > From: Bryan Heitman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 31, 2004 2:53 PM > To: [EMAIL PROTECTED] > Subject: InnoDB Deadlock cannot find free slot for undo > > Looking for some help on tuning my InnoDB settings. I received a InnoDB > deadlock. > > From analyzing show innodb status --> > * There were a ton of processes in the active status not doing anything. > * The log flushed up to was moving but the last checkpoint at was > extremely > old. > > Error in mysql error log scrolling repeatedly: > 16:21:37InnoDB: Warning: cannot find a free slot for an undo log. Do you > have too many active transactions running concurrently? > > version | 4.0.17-standard-log > > current innodb settings > set-variable = innodb_buffer_pool_size=768M > set-variable = innodb_additional_mem_pool_size=20M > set-variable = innodb_log_file_size=256M > set-variable = innodb_log_files_in_group=3 > > Any help would be appreciated. > > Best, > > > Bryan Heitman > [EMAIL PROTECTED] > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
