Monday, January 16, 2017

Channels - Unable to use redis as sharded cluster

Hi,

I am using django channels for production.

I have configured redis on AWS Elastic-cache  as sharded cluster.

  File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    utility
.execute()
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 346, in execute
   
self.fetch_command(subcommand).run_from_argv(self.argv)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/django/core/management/base.py", line 394, in run_from_argv
   
self.execute(*args, **cmd_options)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/django/core/management/base.py", line 445, in execute
    output
= self.handle(*args, **options)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/channels/management/commands/runworker.py", line 64, in handle
    worker
.run()
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/channels/worker.py", line 79, in run
    channel
, content = self.channel_layer.receive_many(channels, block=True)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/asgi_redis/core.py", line 129, in receive_many
    result
= connection.blpop(list_names, timeout=self.blpop_timeout)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/redis/client.py", line 1163, in blpop
   
return self.execute_command('BLPOP', *keys)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/redis/client.py", line 573, in execute_command
   
return self.parse_response(connection, command_name, **options)
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/redis/client.py", line 585, in parse_response
    response
= connection.read_response()
 
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/redis/connection.py", line 582, in read_response
   
raise response
redis
.exceptions.ResponseError: CROSSSLOT Keys in request don't hash to the same slot

It works very well with single node, but getting error if I use sharded instance.

Thanks in advance.
-Dadaso



Disclaimer
This email communication (including any attachments) contains information which is confidential and may be legally privileged. It is for the exclusive use of the intended recipient/s. If you are not the intended recipient, please delete this email communication (including any attachments) and hard copies immediately, please preserve its confidentiality and notify the sender. Any unauthorized use or dissemination of this email communication (including any attachments) in any manner whatsoever, in whole or in part, is strictly prohibited. This email communication (including any attachments), may not be free of viruses, you should carry out your own virus checks before opening any attachment to this e-mail. The sender of this e-mail and Cuelogic Technologies shall not be liable for any damage that you may sustain as a result of viruses, in completeness of this message, a delay in receipt of this message. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Cuelogic Technologies. Cuelogic Technologies will not accept any liability in respect of such content of this email, and the author shall be solely responsible and will be personally liable for any damages or other liability.

--
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/d7e9bfba-f82c-401f-ad35-8fd1fb16fe5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment