Support Single Configuration Endpoint for Redis broker/result-backend

[aivrit]

Hi, The logic of picking the implementation backend for a broker/result-backend for redis is based on the number of redis hosts explicitly written in the connection string, as was implemented in #459 That's great, but does not support using a single configuration endpoint for auto-discovery of the cluster's hosts, as commonly used for example with aws elasticache redis. perhaps adding support for that could simply be to always be using the go-redis backend instead of the redigo? or adding a config parameter to control that instead of the hard-coded behavior? Would love to hear your thoughts. Thanks!

[danie1Lin]

https://github.com/RichardKnop/machinery/pull/712 I encountered this problem a few days ago, so I made a draft to add this feature. Please feel free to give me some advice to make it better.

[danie1Lin]

Hi @aivrit, the pr is already merged to master, perhaps you can try it.