Timeline for Too Many database connections on Amazon RDS
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2014 at 15:16 | comment | added | mustaccio | May be you should consider implementing some sort of connection pooling. | |
| Jul 10, 2014 at 14:58 | comment | added | user43522 | AWS sets the max connections based on the size of your instance. the formula they use is: max_connections = {DBInstanceClassMemory/12582880} See the Parameter Groups documentation: https://console.aws.amazon.com/rds/home?region=us-east-1#parameter-groups: | |
| Jul 6, 2013 at 5:45 | comment | added | TomTom | Not being a MySql / Linux guy - how can you have 100+ connection from one website? I do asp.net only, and any of my pages only opens ONE connection at a time - so that would mean processing 100+ pages at the same time (actually more as a page only has a connection open while needing it). I would look into your approach of handling the connections - that is seriously inefficient. | |
| Jun 6, 2013 at 4:41 | comment | added | Peter Venderberghe | You can use MONyog- MySQL Monitor which has PROCESSLIST based sniffer helps in Notifying and KILLING of long running queries. It works well with Amazon RDS too. | |
| Jun 5, 2013 at 19:54 | comment | added | Michael - sqlbot | Killing the query via an automated process seems like entirely the wrong approach... whether your RDS instance is in fact underpowered, causing the initial pileup... or there's something wrong with the logic in your application, it seems like finding the actual problem with the query would be the thing to do... | |
| Jun 5, 2013 at 19:38 | history | edited | RolandoMySQLDBA |
edited tags
|
|
| Jun 5, 2013 at 19:30 | answer | added | RolandoMySQLDBA | timeline score: 8 | |
| Jun 5, 2013 at 19:26 | review | First posts | |||
| Jun 5, 2013 at 20:18 | |||||
| Jun 5, 2013 at 19:10 | history | asked | ConcernedCEO | CC BY-SA 3.0 |