Recently, I rebooted one of my RDS (Mysql) instance, as it was hanging every now and then. What should have been a breeze, became stormy. Instance rebooted, and picked wrong Parameter Group. The parameters, understandably, were not set with this instance in mind. The instance went in incompatible-parameters Status (i.e. DB Instance Status). I figured the issue, and tried to change the right parameter group. BUT, because instance is in incompatible-parameters Status, the change will not be allowed. I tried looking with our friend Google on how to get my instance in Available status again, only to find that people already are in distress, from as long as 2010. There have been no plausible and easy solution to do this. Refer following https://forums.aws.amazon.com/thread.jspa?threadID=237385 https://forums.aws.amazon.com/thread.jspa?messageID=587725 https://forums.aws.amazon.com/thread.jspa?threadID=55800 BTW, I cannot change my Parameters Group values, as that Group is bei
Showing posts from August, 2016
- Other Apps
Faced it recently!! The Client request is sending large data set to Server. Till date it worked fine on our Test & Staging servers. Put it on Live, and Kaput!! Checked it across various clients, i.e. iOS, Android, Postman etc. Worked on all, but iOS. Increased time outs for Live to check, but still the same. Eventually figured, Amazon ELB (Load Balancer) is timing out. ELB's idle timeout was 60 seconds. Increased it to 180 seconds, and Voila! it worked. Load Balancers are nifty machines to help with keeping one address for outside world, and contain multiple sub addresses internally. ELB accepts the HTTP/HTTPs request which contains the large data set, and maintain a connection with the Client (along with a connection with Server). If client / instance does not send data in the duration specified in idle_timeout, the connection is closed by ELB.