GitHub user static-moonlight edited a comment on the discussion: Airflow cli 
response times

Based on your information I suspected the python environment itself and 
potentially the available computing resources (our test environment is not that 
good, but it's what I have available).

I'm using the off-the-shelf container image (`docker.io/apache/airflow:3.2.2`), 
which has a ton of providers already bundled. Roughly 30 of them, from which I 
might need a third or so. But since providers seems to be lazy loaded by 
default, and I didn't change that, I don't really think it's the providers.

As I said, our dedicated testing hardware is a bit slow, especially in the IO 
and networking area. On a hunch I tried to execute a simple Airflow command 
with no database configuration.

got ya ...

```
$ time airflow --help
Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 3, in <module>
    from airflow.__main__ import main
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/__init__.py", 
line 81, in <module>
    settings.initialize()
    ~~~~~~~~~~~~~~~~~~~^^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/settings.py", 
line 801, in initialize
    configure_vars()
    ~~~~~~~~~~~~~~^^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/settings.py", 
line 262, in configure_vars
    SQL_ALCHEMY_CONN_ASYNC = 
_get_async_conn_uri_from_sync(sync_uri=SQL_ALCHEMY_CONN)
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/settings.py", 
line 243, in _get_async_conn_uri_from_sync
    scheme, rest = sync_uri.split(":", maxsplit=1)
    ^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

real    0m4.578s
user    0m4.391s
sys     0m0.145
```

It looks like as if the `airflow` CLI command is always trying to talk to the 
database, even for a simple `--help`, and starts crying when it fails :) And 
with slow IO in our testing environment, I think the problem might be in that 
direction.

It would be interesting though why Airflow is ALWAYS trying to talk to the 
database, even for that. For everything else it kind of makes sense, since the 
database seems to be used as some kind of middleware and service registry as 
well.

GitHub link: 
https://github.com/apache/airflow/discussions/68707#discussioncomment-17365225

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to