Redis issue when editing products in Magento 2.3

Hello, non-techie here. Lots of detail – questions at the end.

I recently (September 2020) migrated from Magento 1.9 to 2.3. Within about 6 weeks, I started getting Redis error messages when editing products. I get the following error message when I go to save after editing a product: Notice: Redis::exec(): send of 8192 bytes failed with errno=32 Broken pipe in /chroot/home/afd62225/ on line 1119

Note: I have BSS Commerce Magento 2 Product Grid Inline Editor installed which I use to edit inventory qty, enable/disable, SKUs, etc. However, it cannot be used to add new products or change in-stock status.

Once I get the error message, I cannot do anything with products EXCEPT within the Product Grid Inline Editor until my hosting company clears it out. I can still update items in the Grid Inline Editor but cannot change in stock status, change categories, edit the description, add new products, etc. This tends to go on for days, even as much as a week.

I host my site on Nexcess. My tech people who migrated me say it is a hosting issue. There have been multiple explanations from Nexcess for the error:

a. I am getting the error incorrectly: Reviewing the memory usage, peak memory used was 2.3G out of 3.0G. The max memory usage was 80%. $ redis-cli -s /var/run/redis-multi-afd62225.redis/redis.sock info memory| egrep “peak_|human” | grep -v system used_memory_human:1.88G used_memory_rss_human:2.12G used_memory_peak_human:2.36G used_memory_peak_perc:79.98% used_memory_lua_human:37.00K maxmemory_human:3.00G So we are not sure what is causing this error, as there is available memory.

b. That it was a set up issue: When the domain was changed to the path in the cron had not been changed.

c. That there was another set up issue: The task to clear out invalidated indexes has not been running. This allows the page cache index keys to grow indefinitely until eventually consuming all of the Reds memory.

d. That I need to change the page cache to Varnish, which I may have to do for an additional $20+ per month: Given that the issues with Redis are being caused by your page cache, I would also recommend transitioning the page cache to Varnish. Varnish has many advantages over Redis when used for page cache. Additionally, this will reduce usage of redis to only backend cache and sessions, which would further alleviate issues regarding Redis memory usage.

They are now saying this is a known issue in 2.3.4 that is fixed in 2.3.5. My tech team wants to charge $600 to upgrade my brand new Magento 2 store.


  1. Anyone have this issue and know what causes/fixes this?
  2. Will Varnish or upgrading to Magento 2.3.5 REALLY fix it or am I throwing money away?
  3. If so, upgrading, is $600 a decent price?


submitted by /u/Dangerous-Rabbit-781
[link] [comments]