Closed sharathm closed 8 years ago
The exact line and a comment is:
/* Can't handle OOM for now. */
assert(redisReaderFeed(r->reader, data, length) == REDIS_OK);
So maybe you're running out ouf memory?
I am running two EC2 instances..
One t2.micro (1GB Mem, 2GB Swap)
and one t2.small (2GB Mem, 8GB Swap)
.
On both of them my application crashes... and for such low number of keys?
Is there any recommendation for what kind of hardware is best suited for the load I have given above?
There's not much I can do here. Closing for now. If this reappears feel free to open again, hopefully with more information or a way to reproduce.
Hi All,
We are currently using
node-redis
to connect to a ElastiCache instance. Everything runs fine for a while.. but, we see the following error in our nodejs application..After this, our application crashes and needs to be restarted.
At first we thought it might be a availability issue since we were running a single instance inside a cluster. Then we thought it might be memory issue and so we upgraded our EC2 instances.
We do experience some peak in our load but that is ~4000 keys being written to ElastiCache. ElastiCache does not show any signs of down time.
Can anyone shed some light as to what could be going on here?
We are running..
node 4.3.1
node-redis 2.4.2
node-hiredis 0.4.1