4

I have a set of AWS Elastic beanstalk using Docker based configuration for both web server and worker server. The way we have setup is that the java process inside docker allocates 70% of the box memory when starting.

Now the first deployment works fine, but when I try to update application version with in-place Rolling update, Elastic beanstalk tries to start an additional docker container with the java process before stopping the existing one. This fails the deploy as the Java server is not able to allocate the required memory. Is there a way that I can setup AWS to kill the old docker instance before starting the new one during deployment?

I even tried Rolling with additional batch, but that one only works for the first batch and then fails for subsequent ones.

Ankit
  • 3,878
  • 5
  • 35
  • 51
  • Are you using Multicontainer Docker environments or Single Container Docker environments? Are you using a single-instance environment or a a load balanced environment? I guess this is really important information in order to make an educated guess here ;) – Martin Löper Apr 03 '20 at 00:44
  • single container, load balanced multiple instances. – Ankit Apr 06 '20 at 23:16
  • Configure `MinInstancesInService` in `aws:autoscaling:updatepolicy:rollingupdate` namespace to `0`. – Oluwafemi Sule Apr 08 '20 at 07:36

1 Answers1

2

immutable updates can be the way to go for you, it basically recreates the EC2 instances completely on every deploy

  1. Open the Elastic Beanstalk console.
  2. Navigate to the management page for your environment.
  3. Choose Configuration.
  4. In the Rolling updates and deployments configuration category, choose Modify.
  5. Select immutable on deploy policy
  6. Apply

you can check more on how it works here

xploshioOn
  • 4,035
  • 2
  • 28
  • 37