potiuk opened a new pull request, #76084: URL: https://github.com/apache/airflow/pull/76084
From 2026-10-25 to 2026-10-30, AWS reclaimed 911 of the 16,145 Spot runners RunsOn launched in us-east-2 (5.6%), at the median 7 minutes after launch, and each interruption reruns the whole job. About half of those interruptions came from a few instance families that made up an eighth of the Spot launches (CloudTrail `BidEvictedEvent`s matched to the `CreateFleet` launches): | Family | Spot launches | Reclaimed | |---|---|---| | m5 (and m5n, m5d, m5ad, m5dn, which the `m5` prefix pulls in) | 1,007 | 30% (m5.2xlarge: 83%) | | m6a | 437 | 13% | | r6a / r7a / r6in (in-memory runners only) | 217 | 36% / 53% / 34% | | m7a, m7i, m7i-flex, m8i and its variants, m8gd, m7gd | ~12,700 | 0.6–3.9% | This drops m5, m5a and m6a from the x64 templates, and r7a, r6a, r6i from the in-memory one. r7i had too few launches to measure, but AWS Spot Advisor rates it above 20% interruptions at every size in us-east-2, so it goes too; the in-memory runners keep r8i. The arm64 templates are unchanged: none of their families stood out. The other cause is that the CloudFormation stack only uses use2-az1 and use2-az2, whose Spot placement score for these families is 1 against 9 in use2-az3; that needs the stack to move to RunsOn's Terraform module and is handled in apache/airflow-ci-infra. Checks run: `uv run --project dev/breeze pytest dev/breeze/tests/test_selective_checks.py -k "runs_on or runner"` (50 passed), ruff format/check. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Claude Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
