GitHub user abdalhalimalzohbi added a comment to the discussion: RabbitMQOperator task stuck on queued when using CeleryExecutor as core executor
Thank you so much, when using the sequential executor, the operator publishes to the correct external queue and does not get stuck. however with the celery executor, it gets stuck because it mistakenly assigns the queue name as the task executor, which caused the confusion. i removed the airflow-provider-rabbitmq package, created a custom operator, and used pika to handle my use case. GitHub link: https://github.com/apache/airflow/discussions/43351#discussioncomment-11043183 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
