News for hackers. Stuff that matters.
Re:Celery 3.0 has been released by misiti3780 on Saturday July 07, 2012 @01:14PM (#4212138)
im using redis instead of rabbitmq - have had zero problems so far. great work, this project is awesome
Re:Celery 3.0 has been released by conesus on Saturday July 07, 2012 @01:14PM (#4212140)
Are you using redis with slaves? When I do that, celery throws errors when trying to add tasks to my redis queue.
Re:Celery 3.0 has been released by asksol on Saturday July 07, 2012 @01:29PM (#4212182)
what's the error and traceback? (paste at pastie.org or similar)
Re:Celery 3.0 has been released by conesus on Saturday July 07, 2012 @01:35PM (#4212201)
Preface this by saying that I've been successfully and happily using celery since 0.8, which was over 2 years ago. Since 2.0, it's been rock solid. But then I switched from RabbitMQ to redis and when I added redis slaves, it broke.

Here goes: http://pastie.org/4216467

It's probably due to redis' INFO command giving different values. Now would be a great time to get it sorted out, too.

Re:Celery 3.0 has been released by asksol on Saturday July 07, 2012 @01:39PM (#4212211)
About your error, seems strange that a simple info command gives that error, maybe you're running an outdated version of redis-py/redis-server?
Re:Celery 3.0 has been released by conesus on Saturday July 07, 2012 @01:47PM (#4212226)
Latest redis (2.4.15) and using redis-py 2.4.10. Just checked the CHANGELOG for redis-py, which is now at 2.4.13, and voila:

    * 2.4.11
        * Made the INFO command more tolerant of Redis changes formatting. Fix for #217.
Doh! Off by a single patch release. Thanks for the help.

See, folks? Celery is amazing in multiple ways.

Re:Celery 3.0 has been released by misiti3780 on Saturday July 07, 2012 @01:35PM (#4212199)
no i am not, sorry
Re:Celery 3.0 has been released by simonpantzare on Sunday July 08, 2012 @07:27AM (#4214349)
Out of curiosity, why do you use Redis instead of RabbitMQ?
Re:Celery 3.0 has been released by misiti3780 on Sunday July 08, 2012 @12:40PM (#4214948)
because its much easier to configure in my opinion, and i dont really care if messages get lost + i am using it in other parts of my stack so it i decided that instead of bringing in another piece of technology, i would utilize what i already had and keep things less complex