You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried out this project, and it looks like a great use of s3 for concurrent leaderboard updates.
But one thing which I cannot figure out is why put lambda handler never times out, although Redis is never disconnected?
I'm asking because when I use ioredis in some other serverless projects, I always get CloudWatch logs of this type: 2021-06-19T20:15:21.741Z 07d895b8-ffe1-4957-b104-ca36d3476f20 Task timed out after 6.01 seconds ,
and the only way to fix it is to set context.callbackWaitsForEmptyEventLoop = false or to do redis.disconnect
So I'm not sure if you use some other ways of preventing "empty event loop" timeouts, or it just works out of the box?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
I have tried out this project, and it looks like a great use of s3 for concurrent leaderboard updates.
But one thing which I cannot figure out is why
put
lambda handler never times out, althoughRedis
is neverdisconnected
?I'm asking because when I use
ioredis
in some other serverless projects, I always getCloudWatch
logs of this type:2021-06-19T20:15:21.741Z 07d895b8-ffe1-4957-b104-ca36d3476f20 Task timed out after 6.01 seconds
,and the only way to fix it is to set
context.callbackWaitsForEmptyEventLoop = false
or to doredis.disconnect
So I'm not sure if you use some other ways of preventing "empty event loop" timeouts, or it just works out of the box?
Thanks!
The text was updated successfully, but these errors were encountered: