You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jobs@airflow.apache.org by GitBox <gi...@apache.org> on 2026/07/08 22:18:59 UTC

[GH] (airflow/redshift-cancel-statement-on-user-kill-deferred): Workflow run "Tests (AMD)" failed!

The GitHub Actions job "Tests (AMD)" on airflow.git/redshift-cancel-statement-on-user-kill-deferred has failed.
Run started by GitHub user steveahnahn (triggered by steveahnahn).

Head commit for run:
bde227ddbf2b6ba2321cc5cb805d5453b9d2a3b1 / Steve Ahn <38...@users.noreply.github.com>
Cancel the Redshift statement when a user kills the deferred task

A deferred RedshiftDataOperator parks its query in the triggerer, so the
operator's own on_kill no longer runs once the task is deferred. When a user
marks that task failed, clears it, or marks it success, the trigger had no
on_kill hook, so the Redshift statement kept running against the cluster or
workgroup even though the operator already cancels the statement on kill in
the non-deferred path. On Redshift Serverless a runaway statement keeps
billing RPU-hours, and on a provisioned cluster it holds a WLM slot, until it
finishes on its own.

This adds on_kill to RedshiftDataTrigger to cancel the running statement when
the user acts on the deferred task, matching the behaviour already shipped for
the EMR, Dataproc, BigQuery, and Dataflow triggers. A cancel_on_kill flag on
both the operator and the trigger lets users opt out.

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

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: jobs-unsubscribe@airflow.apache.org
For additional commands, e-mail: jobs-help@airflow.apache.org