apache / airflow

Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
https://airflow.apache.org/
Apache License 2.0
37.12k stars 14.3k forks source link

Airflow 1.10.14 - celery worker doesn't want to connect to redis. #14100

Closed Rudasek86 closed 3 years ago

Rudasek86 commented 3 years ago

Apache Airflow version: 1.10.14

Kubernetes version (if you are using kubernetes) (use kubectl version):

Environment: Red Hat Enterprise Linux 8.2 (VMware)

What happened:

We have upgraded version of airflow from 1.10.2 to 1.10.14 and there is a problem to connect to redis by celery worker. This is really wierd problem because when we run a airflow celery worker (without -D parameter) it's connecting without problem. In Flower tool we can see redis connection is online, but when we try do it with -D, airflow celery worker -D there are errors like below.

[2021-02-04 17:33:00,442: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 107 connecting to redis:6379. Operation on closed file.. Trying again in 12.00 seconds... (6/100) Before upgrade on version 1.10.2, we didin't have a problems like that. Our configuration has been working with settings broker_url = redis://localhost:6379/0

Of course our redis is working on default port on this same machine netstat-ntlp

tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN -

Now we have a settings IN airflow cfg we have setting like below:

broker_url = redis://localhost/0 We have tried also settings like below:

broker_url = redis://localhost:6379/0 broker_url = redis://127.0.0.1/0 broker_url = redis://127.0.0.1:6379/0 broker_url = redis://redis:6379/0 broker_url = redis://redis/0

What you expected to happen:

We would like to connect to redis on airflow celery deamon functionality.

We do not really know, redis server version is this same, when airflow 1.10.2 was connecting sucessfully. Later Version of airflow and redis client has been upgraded.

How to reproduce it:

Anything else we need to know:

boring-cyborg[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the issue template!