05-25-2016, 08:17 AM (This post was last modified: 05-25-2016, 01:05 PM by spjonez.)
(05-25-2016, 06:12 AM)Narf Wrote: Unfortunately, until you figure out that last point, nobody would be able to help.
Can you think of any Redis settings that could cause this? What's really odd is that I never see the error when I'm developing locally with Redis installed on my machine. The only time I can produce the error is in our staging/production environments on AWS. Redis is a separate Elasticache Server it's not installed on the web nodes- they're load balanced with Elasticbeanstalk. Scratch that, I was able to trigger it on my local machine by triggering two concurrent AJAX requests. It doesn't happen every time I'll try to narrow down a set of actions that can trigger it reliably.
On AWS I'm running Redis 2.8.24 the latest version they have available. Locally I've tried both 2.8.24 and 3.02 and cannot reproduce the error. It's difficult to reproduce on staging but happens very frequently on production. Could Redis be running out of memory?
Here's a screenshot of the parameter group and some metrics, do either of these help? I managed to trigger it a few times on staging and attached the stack trace.
Testing notes:
1. The error occurs with Redis installed on the same machine (Macbook) and when it's a separate server (AWS).
2. I can make our app fire 3 concurrent AJAX requests and it does not trigger the error. I was able to trigger it with two in dev, once.
3. It's not tied to aborting AJAX requests. I can make that happen with a certain set of actions and the error doesn't appear.
