Howdy. Take a look at this article:

http://www.mysqlperformanceblog.com/2007/02/25/pitfalls-of-converting-to-innodb/


--
-- Tom Mornini, CTO
-- Engine Yard, Ruby on Rails Hosting
-- Support, Scalability, Reliability
-- (866) 518-YARD (9273) x201



On Jan 21, 4:11 am, Stanislav Bozhkov <[EMAIL PROTECTED]
s.net> wrote:
> Hi,
>
> My application throws some "Mysql::Error: Lock wait timeout" from time
> to time. I think it coincides with the upgrade of Rails to version 2.0.2
> .
>
> The exact error is this:
> =========================
>  Mysql::Error: Lock wait timeout exceeded; try restarting transaction:
> INSERT INTO `sessions` (`updated_at`, `session_id`, `data`)
> VALUES('2008-01-20 06:31:40', '34264f71fed074a320ed77dda7a86bda',
> 'BAh7CDoKdG9waWMiEdCS0YHQuNGH0LrQuDoPc3Zlam9fdHlwZSIKZnJlc2gi\nCmZsYXNoSUM6 
> J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhhc2h7\nAAY6CkB1c2VkewA=\n')
>  /usr/lib64/ruby/gems/1.8/gems/activerecord-2.0.2/lib/active_record/connecti 
> on_adapters/abstract_adapter.rb:150:in
> `log'
> =========================
>
> The sessions table has been generated by rake.
>
> Can anyone give me a clue what could be locking the table.
>
> 10x in advance
> --
> Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to