Upgrading to redis>=3.0 results in failed job about flask-rq2 HOT 8 CLOSED

I ran into this too. rq has an open issue for it rq/rq#1014 They suggest using the following until it is fixed.

redis==2.10.6
rq==0.12.0

from flask-rq2.

Also ran into the issue, pinning to redis 2.10.6 resolved it.

from flask-rq2.

I've released 18.2 that requires RQ < 0.13.0 and redis < 3.0.0 while we wait for the fix in RQ.

from flask-rq2.

rq/rq#1016 has been merged in. I'll wait for a few days before cutting a release, just to be doubly sure that there are no major bugs introduced.

from flask-rq2.

@selwin Thank you!

from flask-rq2.

There is more to do in rq/rq-scheduler#197.

from flask-rq2.

I've published a 18.2.2 release that should fix the version conflict as reported in #75. There is also a 18.3 release that requires redis-py 3.0, rq 0.13 and rq-scheduler 0.9 and fixes this ticket for good. Please use 18.2.2 if you need to stay on redis-py < 3.0.

from flask-rq2.

Using this thread, i've used various combinations of pinning redis, rq, and Flask-RQ2 and still get the error

Moving job to 'failed' queue (work-horse terminated unexpectedly; waitpid returned

I have also made sure my timeout in seconds for the @rq.job decorator is set. Is there a configuration i'm missing here to ensure large jobs are not sent to failed?

from flask-rq2.