ashb commented on pull request #14531:
URL: https://github.com/apache/airflow/pull/14531#issuecomment-789691674
> > If yes, then the Launch Template in eu-central-1 defines the instance
size, and the user-data defines how big we mount the /var/lib/docker --
cloud-init.yaml lives in the airflow-ci-infra repo and (for now) needs to be
manually updated in AWS on change. Command is in the commit that added it.
>
> Do I need to do anything - like restart the machines etc. to be sure that
new changes are in effect?
Restarting the machines would kill in-progress jobs. If you just leave it,
then over time as they become idle and get replaced new ones will come up. So
no, just make the change and wait is the best plan.
I recommend adding a column of "LaunchTemplate version" to the EC2 Instances
dashboard, or I have this snippet I run to see what instances are doing.
```bash
watch "~/.virtualenvs/awscli/bin/aws --profile airflow autoscaling
describe-auto-scaling-groups | jq '.AutoScalingGroups[0].Instances[] |
{state:.LifecycleState, protected: .ProtectedFromScaleIn, ver:
.LaunchTemplate.Version, id:.InstanceId}' -c | sort -r"
```
(`protected:true` means that instance is currently executing a job).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
