In T415661, we configured Airflow to store XCOM values larger than 256KB into S3. We need to take care of the garbage collection of these values, after a delay of, say, 7 days.
Description
Description
Details
Details
Related Changes in GitLab:
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Deploy the XCOM cleaner DAG to all instances | repos/data-engineering/airflow-dags!1997 | brouberol | T415777 | main | |
| Add a DAG factory to cleanup old XCOMs from S3 | repos/data-engineering/airflow-dags!1986 | brouberol | T415777 | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Antoine_Quhen | T411988 Airflow main performance instance optimization | |||
| Resolved | BUG REPORT | JAllemandou | T412003 Airflow-main scheduler loop sometimes slows down markedly | ||
| Resolved | brouberol | T415661 Automatically put large Airflow XCOM values in S3 | |||
| Resolved | brouberol | T415777 Schedule the regular cleanup of large XCOM values from S3 |
Event Timeline
Comment Actions
I've opened a patch (https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/1986) that cleans up XCOMs that are > 30d
Comment Actions
brouberol merged https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/1986
Add a DAG factory to cleanup old XCOMs from S3
Comment Actions
brouberol merged https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/1997
Deploy the XCOM cleaner DAG to all instances