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'm using this amazing cache/cache store in an AWS lambda function and noticed that it was hanging open without terminating. I managed to fix this by doing something like this:
redisCache.store._pool.drain();
When my app is finished. Is this correct? Am I guaranteed that the cache entries have been written? (I don't wait for them when doing set).
If so I think there should be a better way to do this or at least a word about it in the readme.
The text was updated successfully, but these errors were encountered:
Actually this is more complicated then expected. If the pool is drained but you have caches outside the lambda handler (which will live until AWS decides to kill the instance), those caches will not work because pool is draining and cannot accept work.
Hi there!
I'm using this amazing cache/cache store in an AWS lambda function and noticed that it was hanging open without terminating. I managed to fix this by doing something like this:
When my app is finished. Is this correct? Am I guaranteed that the cache entries have been written? (I don't wait for them when doing
set
).If so I think there should be a better way to do this or at least a word about it in the readme.
The text was updated successfully, but these errors were encountered: