- πΊπΈUnited States Elijah Lynn Portland, Oregon
Thanks for this! I had this issue on an AWS Elasticache Memcache and fixed it by creating a custom param group and changed the value `max_item_size` to `4194304` (which is 4M) for our needs which resolved the error.
- πΊπΈUnited States DamienMcKenna NH, USA
Even with the config set to 5M the error still happens :-\
In this latest case the site was reindexing the content on a Solr server with Search API.
- Status changed to Closed: cannot reproduce
over 1 year ago 12:31am 6 December 2023 - πΊπΈUnited States japerry KVUO
Closing as this isn't really an issue in the module per se.
- Assigned to DamienMcKenna
- Status changed to Active
over 1 year ago 1:54am 6 December 2023 - πΊπΈUnited States DamienMcKenna NH, USA
Let's add this to the docs as a Known Issues item, or something similar. Assigning it to myself in the hopes I might throw something together for it.
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 7:46pm 2 April 2024 - πΊπΈUnited States DamienMcKenna NH, USA
How about something like this?
-
japerry β
committed ae689e0c on 8.x-2.x
Issue #3303674 by DamienMcKenna: "object too large for cache" error
-
japerry β
committed ae689e0c on 8.x-2.x
- Status changed to Fixed
9 months ago 11:03pm 3 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.