Hi guys,

recently switched to percona 5.5 and started having "too many connections" 
exceptions

i noticed that exceptions started popping up on the very first slave we 
pushed into the pool so it seems like after redeploy rails does not kill old 
connections to mysql

anyone had such problem before?

i guess options are to: 
- drop inactive connections on mysql side
- handle deploy shutdowns better
- stop using persistent connections

does this even make sense?

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/rubyonrails-core/-/0w-FWQAxn6EJ.
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-core?hl=en.

Reply via email to