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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
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. Regards, Ben Langfeld On Wed, Aug 17, 2011 at 9:10 AM, Maksym Melnychok <keymone@gmail.com> wrote:> 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 rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Agreed. This is not a rails-core issue. Please ask this on the rubyonrails-talk mailing list instead. On Wednesday, 17 August 2011 at 7:55 PM, Ben Langfeld wrote:> 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. > > Regards, > Ben Langfeld > > > On Wed, Aug 17, 2011 at 9:10 AM, Maksym Melnychok <keymone@gmail.com (mailto:keymone@gmail.com)> wrote: > > 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 rubyonrails-core@googlegroups.com (mailto:rubyonrails-core@googlegroups.com). > > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com (mailto:rubyonrails-core%2Bunsubscribe@googlegroups.com). > > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-core@googlegroups.com (mailto:rubyonrails-core@googlegroups.com). > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com (mailto:rubyonrails-core+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.