tg295 opened a new issue #21467:
URL: https://github.com/apache/airflow/issues/21467
### Apache Airflow version
2.2.1
### What happened
I have a number of DAGs that involve processing reports that arrive at a
regular frequency which are then sent to a database. Some of these reports have
lead times (or lag times), meaning it will take at least a day or two for them
to be generated. To accommodate for this I was utilising airflows
DateTimeSensor, so that for a given execution date the task will wait for the
allotted amount of time before moving to the next task where it downloads the
corresponding report.
This was working fine however I have recently noticed a number of
DateTimeSensor tasks failing and I can't quite figure out why.
Here is an example snippet of the traceback:
```[2022-01-31, 06:30:22 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 07:30:22 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 08:30:22 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 09:30:22 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 10:30:22 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 11:30:22 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 12:30:23 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 13:30:23 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 14:30:23 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 15:30:23 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 16:30:23 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 17:30:23 UTC] {date_time.py:73} INFO - Checking if the time
(2022-02-01) has come
[2022-01-31, 17:50:53 UTC] {local_task_job.py:212} WARNING - State of this
instance has been externally set to up_for_retry. Terminating instance.
[2022-01-31, 17:50:53 UTC] {process_utils.py:100} INFO - Sending
Signals.SIGTERM to GPID 238
[2022-01-31, 17:50:53 UTC] {taskinstance.py:1411} ERROR - Received SIGTERM.
Terminating subprocesses.```
N.B. Currently I have `retries=1`.
### What you expected to happen
_No response_
### How to reproduce
_No response_
### Operating System
Linux
### Versions of Apache Airflow Providers
_No response_
### Deployment
Other Docker-based deployment
### Deployment details
Multi-container setup deployed via Docker Swarm. w/ Celery Executor,
RabbitMQ, Flower, Postgres.
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
