add_consumer is not working when the broker is set to use SQS

13 views
Skip to first unread message

Rogério Alexandre Machado Carrasqueira

unread,
Oct 26, 2019, 2:38:18 PM10/26/19
to celery-users
Hello All!

I'm using Celery 3.1 with Django 1.4.22 and I want to move from RabbitMQ to SQS. I've setup the celery and all scheduled tasks are running as well. But when I have to use the method add_consumer, the jobs are not consumed by the worker and no response from then. See what I'm doing:

>>> from celery import current_app as app                     

>>> app.control.add_consumer('production-email-campaign-105258', reply=True, destination=['celery@worker_email.w13.ip-10-0-1-82'])

[]

>>> app.control.add_consumer('production-email-campaign-105258', reply=True, destination=['celery@worker_email.ip-10-0-1-82'])

[]

>>> app.control.add_consumer('production-email-campaign-105258', reply=True, destination=['celery_worker_email-ip-10-0-1-82-celery-pidbox'])

[]

>>> app.control.add_consumer('production-email-campaign-105258', reply=True)

[]

>>> app.control.add_consumer('production-email-campaign-105258', reply=True, destination=['celery_worker_email-ip-10-0-1-82'])

[]

>>> 


I did not get any response from the celery and jobs to remain to wait for consumer. I would like to know if there any clue to make celery working good with SQS and dynamic queues, as example 'production-email-campaign-XXX' that is created on the fly.


Thanks


Rogério

Reply all
Reply to author
Forward
0 new messages