The GitHub Actions job "Tests (AMD)" on 
airflow.git/feature/celery/mp-start-method has failed.
Run started by GitHub user jason810496 (triggered by jason810496).

Head commit for run:
971a123dee955e88955444cf0567ddb941cf6899 / LIU ZHE YOU <[email protected]>
Add Celery worker mp_start_method config to curb Python 3.14 memory

Python 3.14 changed the Unix multiprocessing default from fork to forkserver
(gh-84559). The Celery worker starts its log server and the stale-bundle-cleanup
loop (and the optional SecretCache manager) as stdlib multiprocessing.Process
children. Under forkserver each re-imports Airflow and spins up extra
forkserver/resource-tracker processes, so a 3.13 to 3.14 upgrade inflates the
worker's resident memory even though nothing about the workload changed.

A new [celery] mp_start_method (falling back to [core] mp_start_method) lets a
deployment pin fork to restore the pre-3.14 behaviour. It governs only the
worker's stdlib multiprocessing helpers; Celery's prefork pool is driven by
billiard, which keeps its own fork default and is unaffected either way.

Report URL: https://github.com/apache/airflow/actions/runs/28224017745

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to