Hi! Do you by any chance have any proxy on top of Redis? Seems like Django has nothing to do with it, though.
I don't know anything about dynamodb really, but I think implementing Django cache with dynamo as backend should work. I've implemented Redis Cluster cache for my project and it works fine. Here're the docs about session engines: https://docs.djangoproject.com/en/1.10/topics/http/sessions/#using-cached-sessions <https://docs.djangoproject.com/en/1.10/topics/http/sessions/#using-cached-sessions> > On 6 Dec 2016, at 15:55, Andreas Kuhne <[email protected]> wrote: > > Hi, > > We are having a strange problem with our redis elasticache instances on AWS. > We have our sessions stored in a redis cluster on AWS. Our webservers > sometimes get a: > * Error connecting to redis.example.com:6379 > <http://redis.example.com:6379/>. timed out > * Timeout reading from socket > > (I haven't included our real domain for the redis servers :-)) > > Both of these are related to our webservers connecting to our redis server. > This started about a month ago, and worked perfectly for nearly 2 years > before that. I really don't understand why this is happening. I know that the > webservers have access to the redis servers, so I really can't understand the > problem. Has anyone else experienced a similar problem? > > That was the first part of my question, my second is related to this though. > For costsaving I would really like to dump the redis cluster and change to a > dynamodb based session store. I have found a pypi package that works for the > implementation, but when I tried it about 2 years ago, it failed miserably. > We ended up having people get new sessions all the time and the sessions > weren't being persisted corrrectly (each request ended up generating a new > session). > > Has anyone successfully implemented a session store on dynamodb? With 2 > webservers behind an loadbalancer? > > Also, has anyone any ideas of how to move the sessions from our redis store > to the dynamodb database? > > Any tips / tricks would be very appreciated. > > Regards, > > Andréas > > > -- > 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 [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/django-users > <https://groups.google.com/group/django-users>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CALXYUb%3D89GTJ33FgE_DpjofdgOn2fYqVoctzo00NOq5K26Twmw%40mail.gmail.com > > <https://groups.google.com/d/msgid/django-users/CALXYUb%3D89GTJ33FgE_DpjofdgOn2fYqVoctzo00NOq5K26Twmw%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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 [email protected]. To post to this group, send email to [email protected]. 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/13E0B717-29E6-43D5-AAD9-0FD4A4424186%40gmail.com. For more options, visit https://groups.google.com/d/optout.
