mysql connections problem

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?

The obvious omission from your post is the platform on which you deploy rails. This is where responsibility lies, and it doesn’t sound like this is a rails-core issue.

Ben Langfeld

Agreed. This is not a rails-core issue. Please ask this on the rubyonrails-talk mailing list instead.