[
https://issues.apache.org/jira/browse/AIRFLOW-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913053#comment-16913053
]
Liang Chen commented on AIRFLOW-5272:
-------------------------------------
I figured it out, two workaround:
1. export {color:#000000}CELERY_CONFIG_MODULE variable before run 'airflow
flower'{color}
{color:#0000ff}export{color}{color:#000000}
CELERY_CONFIG_MODULE=airflow.config_templates.default_celery {color}
2. instead of 'airflow flower', use flower command with
{color:#FF0000}config{color}:
{color:#000000}flower -b
{color}{color:#a31515}'sentinel://192.168.1.1:26379;sentinel://192.168.1.2:26379'{color}{color:#000000}
--address=0.0.0.0 --port=5555
--config=airflow.config_templates.default_celery{color}
> Flower is not working with Redis Sentinel
> -----------------------------------------
>
> Key: AIRFLOW-5272
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5272
> Project: Apache Airflow
> Issue Type: Bug
> Components: celery, cli
> Affects Versions: 1.10.3
> Reporter: Liang Chen
> Priority: Critical
>
> Flower is hang and not accessible via link (HTTP TIMEOUT) if broker url use
> Redis Sentinel.
> Scheduler and Worker are working fine.
> No Flower error message displayed in log.
> After checking code, I can see {color:#000000}broker_transport_options is not
> passed to Flower, master_name is None. {color}
>
> related issue: AIRFLOW-966
> ======= config ========
> {color:#000000}[celery]{color}
> {color:#0000ff}broker_url{color}{color:#000000} =
> sentinel://192.168.1.1:26379{color}{color:#008000};sentinel://192.168.1.2:26379;sentinel://192.168.1.3:26379;sentinel://192.168.1.4:26379{color}
> {color:#000000}[celery_broker_transport_options]{color}
> {color:#008000}#visibility_timeout = 21600{color}
> {color:#0000ff}master_name{color}{color:#000000} = mymaster{color}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
