The latest articles on DEV Community by Ethan (@xipher7934). https://dev.to/xipher7934 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F457694%2F18f98ae4-1bf9-4770-b3e6-f0ae32a9b001.jpeg https://dev.to/xipher7934 en Ethan Tue, 01 Sep 2020 19:32:14 +0000 https://dev.to/xipher7934/stumped-about-rails-connection-limit-error-13i2 https://dev.to/xipher7934/stumped-about-rails-connection-limit-error-13i2 <p>Over the last year I have been getting random ActiveRecord::ConnectionTimeoutError errors, where the application could not obtain a connection from the pool within 5 seconds. But I'm stumped as to what the actual issue is...</p> <ul> <li>we're using an AWS RDS instance that can handle hundreds of connections, which we never even come close to by the RDS connection log (max use is ~30).</li> <li>I have been over forums that talk about using Thread.new... but we don't spin any of our own threads.</li> <li>I've seen forums that talk about workers using more pool connections than necessary, but I haven't set up any puma workers, we just use web instances!</li> <li>There is no consistency in which controller#action throws the error, and no consistency on time of day or week.</li> <li>Sometimes the error will not show up for weeks, and then I'll get 15 instances of it in a few days</li> </ul> <p>I'm at a loss as to where to even start looking...</p> rails postgres help