You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "WiC-htao (via GitHub)" <gi...@apache.org> on 2024/07/29 02:19:35 UTC
[I] deferrable FileSensor alway get stuck [airflow]
WiC-htao opened a new issue, #41087:
URL: https://github.com/apache/airflow/issues/41087
### Apache Airflow version
Other Airflow 2 version (please specify below)
### If "Other Airflow 2 version" selected, which one?
2.9.1
### What happened?
when i use FileSensor and set deferrable=True,i got the warning, “The triggers does not appear to be running. Triggers will not run, and any deferred operator will remian deferred until it times out and fails”, and the task looks stuck. But everything is good when i set deferrable =False.
I am not sure if this is a bug or I mis-config anything. My python version is 3.8.10 with airflow 2.9.1 using a mysql as a dataset backend on ubuntu 20.04. And code almost running on gpfs file system. I don‘t know whether it doesn't support deferrable operators and cause all of this.
My test code is really simple here.
```
with DAG("dev_test", schedule=None) as dag:
FileSensor(task_id = "test", filepath=“/home/ubuntu/test.airflow”, deferrable=True, poke_interval=30, timeout=300,
```
The only warning message i can find is
```
WARNING - empty cryptography key - values will not be stored encrypted.
```
by the way, `airflow db clean` also doesn't work for me with a warning below, i have to delete the trigger table mannual in sql.
```
WARNING - Encountered error when attempting to clean table 'trigger'
```
### What you think should happen instead?
_No response_
### How to reproduce
```
with DAG("dev_test", schedule=None) as dag:
FileSensor(task_id = "test", filepath=“/home/ubuntu/test.airflow”, deferrable=True, poke_interval=30, timeout=300,
```
And trigger it mannually.
### Operating System
ubuntu 20.04
### Versions of Apache Airflow Providers
_No response_
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
_No response_
### 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: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] deferrable FileSensor alway get stuck [airflow]
Posted by "WiC-htao (via GitHub)" <gi...@apache.org>.
WiC-htao closed issue #41087: deferrable FileSensor alway get stuck
URL: https://github.com/apache/airflow/issues/41087
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] deferrable FileSensor alway get stuck [airflow]
Posted by "boring-cyborg[bot] (via GitHub)" <gi...@apache.org>.
boring-cyborg[bot] commented on issue #41087:
URL: https://github.com/apache/airflow/issues/41087#issuecomment-2254814768
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] deferrable FileSensor alway get stuck [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #41087:
URL: https://github.com/apache/airflow/issues/41087#issuecomment-3135100676
This issue has been automatically marked as stale because it has been open for 365 days without any activity. There has been several Airflow releases since last activity on this issue. Kindly asking to recheck the report against latest Airflow version and let us know if the issue is reproducible. The issue will be closed in next 30 days if no further activity occurs from the issue author.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org