New answers tagged amazon-rds
OK, I resized my TEMP tablespace and that appears to have sorted out my issue. Here's the command I ran: ALTER TABLESPACE TEMP SHRINK SPACE KEEP 512M; Seems to have fixed the issue (DB size went from 19GB to 2GB), but I'm still in the dark about why this would have occurred in such a small environment. Added some CloudWatch alarms so I can jump on this ...
Do non-"PIOPS Optimized" instances still benefit from Provisioned IOPS? Yes. You benefit from the PIOPS volumes being SSDs under the hood. Optimized instances have dedicated network to the EBS servers, so they get consistent performance. Non-optimized instances interact with EBS along with the rest of their network traffic, so heavy bandwidth use on the ...
The only real cons I can see are: lack of PIOPS optimisation for the db.m3.large (where you would have guaranteed bandwidth connecting you to EBS and PIOPS volumes) smaller (albeit faster) instance/ephemeral storage for the m3.large (32GB SSD vs 2x 480GB HDD), and to be honest I'm not sure instance storage is relevant for RDS instances And that's it. ...
according to the AWS RDS documentation db.m1.large is PIOPS-optimized, but db.m3.large is not RDS Instance Classes Standard - Second Generation db.m3.large vCPU:2 ECU:6.5 Memory (GiB):7.5 PIOPS-Optimized:No Network Performance:Moderate Standard - First Generation db.m1.large vCPU:2 ECU:4 Memory (GiB)7.5 PIOPS-Optimized:Yes Network ...
It seems like your RDS instance got hosed. Do you have any snapshots where you can create another one from ? I performed the same operations that you described and my database works fine. You can also check the logs: Hope it helps.
Finally tracked down the cause of our problems. Apache was misconfigured to have a Keep Alive timeout for 30 seconds. That combined with an overly aggressive AJAX script was causing the site to hang and wait for a connection. Turning KeepAliveTimeout down to 7, as well as taming the AJAX script, brought everything back to normal.
Reserved instances are a billing construct only. If you buy a reserved instance for a m1.small in us-west-2a, all that means is that one of your on-demand RDS instances that's an m1.small in us-west-2a receives that lower hourly price (and incidentally, if you delete that instance and make a new one, the reservation's lower hourly rate just shifts onto the ...
The above answer is correct but I wanted to add some extra data as I too had the same requirement and I suspect most people using EB and RDS should have the same requirement too even if they don't know it yet. First, why would you want the RDS instance to exist outside the EB environment? So that the lifetime of the RDS instance is not tied to the lifetime ...
You can also modify query_cache_size and max_allowed_packet parameters via the AWS Management console. Use this AWS documentation as your guide, link
Top 50 recent answers are included