Hello,
We had an incident where the application ended up in error 500 because of memory exhausted.
We narrowed down the issue to the flysystem cache using Redis:
flysystem pushed so many items in this single redis key that it took a lot of memory for PHP to retrieve this object and json_decode it resulting in a memory exhaustion
We have a 196mo memory limit on the prod.
Querying that redis key to check for values made our Redis GUI client crash (TablePlus)
Workaround
I'm not looking for a flysystem v1 fix. The immediate fix was to empty this redis entry.
Question
I'm looking to know if this is a behaviour you're aware of and if this has been fixed in v2 or v3 by implementing a cache eviction / cache limit
Bug Report
Summary
Hello, We had an incident where the application ended up in error 500 because of memory exhausted.
We narrowed down the issue to the flysystem cache using Redis: flysystem pushed so many items in this single redis key that it took a lot of memory for PHP to retrieve this object and
json_decode
it resulting in a memory exhaustionWe have a
196mo
memory limit on the prod. Querying that redis key to check for values made our Redis GUI client crash (TablePlus)Workaround
I'm not looking for a flysystem v1 fix. The immediate fix was to empty this redis entry.
Question
I'm looking to know if this is a behaviour you're aware of and if this has been fixed in v2 or v3 by implementing a cache eviction / cache limit
Example of a value stored inside the cache: