<h1 id="heading-motivation">Motivation</h1>
The initiative of this post is an error that I bumped into in the past for Airflow and I wish to document how to solve it if you came across them. Gonna be short
<h1 id="heading-introduction">Introduction</h1>
The error message is shown below
<pre><code class="lang-yaml">airflow.exceptions.AirflowException: Task received SIGTERM signal
</code></pre>
<h1 id="heading-solution">Solution</h1>
The solution for this problem is to adjust the settings for <code>airflow.cfg</code> you need to locate the key work below
<pre><code class="lang-yaml"># When a task is killed forcefully, this is the amount of time in seconds that
# it has to cleanup after it is sent a SIGTERM, before it is SIGKILLED
killed_task_cleanup_time = 1200
</code></pre>
We need to change this task to an arbitrarily large number (not too large as well)
<pre><code class="lang-yaml"># When a task is killed forcefully, this is the amount of time in seconds that
# it has to cleanup after it is sent a SIGTERM, before it is SIGKILLED
killed_task_cleanup_time = 604800
</code></pre>
the main issue was that the task was receiving a SIGTERM signal before it finished running. We just wait a bit longer and be patient by change the configuration.
<h1 id="heading-reference">Reference</h1>
<ul>
<li><a target="_blank" href="https://github.com/apache/airflow/issues/18041">airflow ticket</a>
</li>
<li><a target="_blank" href="https://stackoverflow.com/questions/54313601/airflow-signals-sigterm-to-subprocesses-unexpectedly">Airflow signals SIGTERM to subprocesses unexpectedly</a>
</li>
<li><a target="_blank" href="https://www.cnblogs.com/braveym/p/12516513.html">Chinese blogger with some interesting posts for Airflow</a>
</li>
</ul>

# Motivation

The initiative of this post is an error that I bumped into in the past for Airflow and I wish to document how to solve it if you came across them. Gonna be short

# Introduction

The error message is shown below

```yaml
airflow.exceptions.AirflowException: Task received SIGTERM signal
```

# Solution

The solution for this problem is to adjust the settings for `airflow.cfg` you need to locate the key work below

```yaml
# When a task is killed forcefully, this is the amount of time in seconds that
# it has to cleanup after it is sent a SIGTERM, before it is SIGKILLED
killed_task_cleanup_time = 1200
```

We need to change this task to an arbitrarily large number (not too large as well)

```yaml
# When a task is killed forcefully, this is the amount of time in seconds that
# it has to cleanup after it is sent a SIGTERM, before it is SIGKILLED
killed_task_cleanup_time = 604800
```

the main issue was that the task was receiving a SIGTERM signal before it finished running. We just wait a bit longer and be patient by change the configuration.

# Reference

* [airflow ticket](https://github.com/apache/airflow/issues/18041)
    
* [Airflow signals SIGTERM to subprocesses unexpectedly](https://stackoverflow.com/questions/54313601/airflow-signals-sigterm-to-subprocesses-unexpectedly)
    
* [Chinese blogger with some interesting posts for Airflow](https://www.cnblogs.com/braveym/p/12516513.html)

Error: Airflow Task received SIGTERM signal

Motivation

Introduction

Solution

Reference