search

cloudcaptainsh / cloudcaptain

Issue Tracker for CloudCaptain
13 stars 3 forks source link

Cannot scale a killed app #207

Open karl-ravn opened 6 years ago

karl-ravn commented 6 years ago

I am trying to deploy new versions of a java8 app, but it takes ut even minutes before we start seeing the first log lines from the service. I've now spent over 4 hours on trying to deploy our app, but it's just not possible.

It's based on spring boot, and maybe once in 10 tries it takes 7-8 seconds to boot the initial spring context, but most of the time it takes over 90. Since we are having it configured to be running with 2 instances, it's practically impossible to make it past the initial boot.

Also, during this, I have tried to "kill" the specific app in our staging environment, and now it won't even let me scale it since it wants to start a 7 months old image that is no longer in the repo.

What should we do? I cannot tear down the whole app just to reconfigure it, because it is running in burning production. It boots just fine on my local computer.

axelfontaine commented 6 years ago

It seems there are multiple things at play here.

  1. Slow start: could this be due to your app or some spring bean waiting for some resource and not finding it/timing out under certain circumstances?
  2. Old image: we'll investigate. I'll keep you updated. Note that you can launch with a new scaling config at the same time when using the CLI instead of the Console, in case this helps.
karl-ravn commented 6 years ago

Ok, somehow, problem number one with the slow start have resolved itself. I have no idea if you did anything or if it is by luck or if there was something off with AWS.

The second issue is still there but of less importance level (at least for me) right now.

Thanks for your very quick response!