amitb2050 opened a new issue, #28655:
URL: https://github.com/apache/airflow/issues/28655

   ### Apache Airflow version
   
   2.5.0
   
   ### What happened
   
   I am trying to set up Airflow Celery to use sentinel. However, we have 
multiple sentinel instances up and running. So referring to the examples on the 
internet, I tried to pass multiple sentinel URL as below in ENV VAR.
   
   
`AIRFLOW__CELERY__BROKER_URL='sentinel://redis_sentinel1:26379;sentinel://redis_sentinel2:26379'`
 (tried with/without quote)
   
   After executing, the worker keeps throwing errors as below:
   
   > Traceback (most recent call last):
   >   File "<string>", line 1, in <module>
   >   File "/usr/local/lib/python3.8/urllib/parse.py", line 177, in port
   >     raise ValueError(message) from None
   > **ValueError: Port could not be cast to integer value as 
'26379;sentinel:'**
   > 
   
   From the error, it looks like the parser is NOT separating sentinel URLs 
with a semicolon separator. Is there any workaround for it?
   
   ### What you think should happen instead
   
   Using a semicolon separator, sentinel URLs should be separated, and the 
Redis connection pool should make use of all the sentinel URLs.
   
   ### How to reproduce
   
   Try to pass multiple sentinel URLs to `AIRFLOW__CELERY__BROKER_URL` 
environment variables and then try to bring up the airflow workers
   
   ### Operating System
   
   ubuntu
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to