Opened 11 years ago
Closed 11 years ago
#380 closed defect (fixed)
SQL: celery/kombu transport database
|Reported by:||Elrond||Owned by:|
celery (and kombu) need a new transport and result database when moving away from mongodb. - celery/kombu and sqlalchemy: `http://docs.celeryproject.org/en/latest/getting-started/brokers/sqlalchemy.html <http://docs.celeryproject.org/en/latest/getting-started/brokers/sqlalchemy.html>`_ - whether a database is actually a good event oriented transport, is an open question. Maybe amqplib and rabbitmq are the better answer? For the result thing we maybe should really use sqlalchemy? Goal of this bug: 1. Research options for celery/kombu 2. come to a conclusion what to use 3. Implement it
Change History (5)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
|Priority:||minor → major|
comment:3 by , 11 years ago
|Milestone:||0.2.1 → 0.2.2|
If we want sql in 0.2.2, we should have an answer to this ticket.
comment:4 by , 11 years ago
Okay, this is ready in cwebber's celerysql branch.
What this branch changes:
- Switch default kombu transport from mongo to sqlalchemy, using a local kombu.db file next to the mediagoblin.ini.
- Switch the result backend for celery from mongo to sqlalchemy, using a local celery.db file next to the mediagoblin.ini.
What does this mean for you?
If you're not running celeryd: Nothing!
If you're running celeryd:
- Install all new dependencies: sqlalchemy, kombu-sqlalchemy. For the future you will need sqlalchemy-migrate also, so just install it too. setup.py has the proper dependencies knowledge, so use it, if you can.
- Remember to restart celeryd and the main MediaGoblin server.
If you're using celeryd in a very special way, especially, if you're using the results in the mongodb, contact us sooner than later, please.
comment:5 by , 11 years ago
|Status:||accepted → closed|
The original url for this bug was http://bugs.foocorp.net/issues/739 .