Publish Message error when use redis as broker about machinery HOT 5 CLOSED

This error may be redigo's bug

from machinery.

@chennqqi I am not sure what is causing the error. This needs to be investigated further.

FYI: #30

There is a bug with chords on Redis. They don't work correctly at the moment. So could be related.

from machinery.

Yeah, I use chords on Redis. I found workers 'ESTABLISHED' too many connections with broker&backend. so that's why publishing tasks failed(wsasend: An existing connection was forcibly closed by the remote host). Each subtask of a chord has a long term connection with broker&backend.

from machinery.

I see. Can you make a PR to fix this?

from machinery.

ok. I will have a try. or I sugguest using nsq or nats instand of redis...
Now, i simply package a chord task (with a lot of subtasks) as a standard task to escape this problem.

from machinery.