Re: Channels/Redis fault tolerance with Twemproxy?

Thanks Andrew,

So with a load-balanced ten web server implementation using Channels (and of course ten instances of redis) do I have a HA solution then?  RIght now Django settings simply has a list of those servers in CHANNEL_LAYERS, what if (say) three of them crash, will Channels continue to try and hash to the dead servers? Again, I'll accept a brief set of errors, but if this effectively causes Channels to continue to error that is not my definition of HA.

Thanks.

On Sunday, July 22, 2018 at 8:09:16 PM UTC-4, Andrew Godwin wrote:

I don't think redis-cluster supports BLPOP properly still so I don't think you can use it.

Andrew

On Sun, Jul 22, 2018 at 12:46 PM Filbert <tim...@gmail.com> wrote:

And just to be clear as to my options, using Channels 2.0 I can use Redis cluster if I have to to get failover and fault tolerance, correct?

On Sunday, July 22, 2018 at 12:57:22 PM UTC-4, Andrew Godwin wrote:

I'm afraid I've never used Twemproxy, so I can't really comment on it, but if you don't care about data loss, it's probably fine?

Andrew

On Fri, Jul 20, 2018 at 3:30 PM Filbert <tim...@gmail.com> wrote:

Going to have 10 or more EC2 instances running Channels 2.0.  I really don't want to add the complexity of Redis Cluster or Redis sentinel.  Is a decent fault tolerant solution to implement Twemproxy, instead.  I don't care about data loss if an instance crashes, but I do care that the application continues to operate on the remaining instances.

Is this a workable solution?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d1d50730-c1ba-4674-8ef8-54294158d0f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/42fe264e-7f1f-426a-82c6-36aed944a923%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/39acd6c1-73e8-46f9-8f39-035d0054c87c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.