Complete cache invalidation on Magento 2.4.6

[ahmed-midori]

Preconditions and environment

• Magento 2.4.6
• We have found that since updating to Magento 2.4.6 we are getting complete cache invalidations if a product changes to out of stock or if a product is edited in admin.

Steps to reproduce

The below issues have been found on a production site as well as a clean Magento install with sample data.

Issue 1 (product changes to out of stock):

If a shipment is created for the last available qty of a product making the product out of stock the complete site cache is invalidated.

Issue 2(Change to a product created in admin):

If any change is made to a product in admin such as change to product title or description then this also completely invalidates all cache site wide.

Expected result

Cache to be invalidated only for the product and the categories containing that product.

Actual result

Complete cache invalidation

Additional information

It is a huge inconvenience and not practical if you are running a site with many categories and 10's of thousands of products to have all cache invalidated just because a single product goes out of stock or a single product is edited.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ahmed-midori. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Dash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Dash, here is your Magento Instance: https://daea483f5e87b5e18cabdeb4db3f15c6.instances-prod.magento-community.engineering
Admin access: https://daea483f5e87b5e18cabdeb4db3f15c6.instances-prod.magento-community.engineering/admin_3f8c
Login: 9d84027c
Password: cf7ce4535a25

[ahmed-midori]

Thank you Rajasekar Panneerselvam for confirming the issue. Im sure you will agree that it is not correct that cache for every single product and pages gets invalidated because one product switches to out of stock. Likewise it is not correct that every product and page gets invalidated if a single product is edited in admin. This is quite frustrating if you have a site with say 30,000 active products and a single product goes out of stock invalidating all 30,000 products. From: Rajasekar Panneerselvam ***@***.***> Sent: Thursday, August 3, 2023 11:58 AM To: magento/magento2 ***@***.***> Subject: Re: [magento/magento2] Complete cache invalidation on Magento 2.4.6 (Issue #37834) Hi @ahmed-midori<https://github.com/ahmed-midori> , Verified the issue in 2.4-develop instance and the issue is reproducible,Hence we are confirming the issue. If we shipment is created for the last available qty of a product making the product out of stock the complete site cache is invalidated and any change is made to a product in admin such as change to product title or description then this also completely invalidates all cache site wide. Kindly refer the below screenshots: [Screenshot 2023-08-03 at 3 16 45 PM]<https://user-images.githubusercontent.com/60198592/258075260-e9b20d4b-ba15-42e0-a367-1642eecf6c15.png> [Screenshot 2023-08-03 at 3 18 11 PM]<https://user-images.githubusercontent.com/60198592/258075320-27c6efc5-f1d9-4368-8923-baa4291c8482.png> [Screenshot 2023-08-03 at 3 20 22 PM]<https://user-images.githubusercontent.com/60198592/258075337-65e2c16e-0f6f-4e92-9d1d-cedeef83295e.png> [Screenshot 2023-08-03 at 3 21 14 PM]<https://user-images.githubusercontent.com/60198592/258075349-6df0b03b-9079-4fae-9dcb-1e3e37a66124.png> [Screenshot 2023-08-03 at 3 21 29 PM]<https://user-images.githubusercontent.com/60198592/258075355-2559545a-186f-49b7-9025-58155f4e9104.png> —

[engcom-Dash]

Hi @ahmed-midori ,

Sorry for inconvenience,

As discussed with internal team,We verified the issue in 2.4-develop instance and its not reproducible.
When we changing the product title and making products get out of stock at the time some of the cache only get invalidated,Kindly refer the below screenshots:
Initially it was idel=0:

After the making product as out of stock:


Thanks.

[ahmed-midori]

Hi @engcom-Dash,

Thank you for your response. Please find below screenshots confirming the issue. You will see screenshots from the homepage, 2 different category pages, 2 different product pages and also a CMS page. All clearly show a cache hit.

As you will see from all the above screenshots all are showing a hit.

I then go to a product as per screenshots below and zero the qty's making the product out of stock:

Following the change of qty to zero/out of stock you will see that cache for everything becomes invalid as per screenshots below:

I can confirm that this cache invalidation occurs with every single product on the website, every single category, the homepage and all cms pages. All by just one product going out of stock.

Further to this and in relation to changes made to a product in admin I can confirm that a change to a product title for example performs exactly the same invalidation to all products, categories, cms pages and homepage.

Surely it cant be normal that in the instance where you have 100,000 products all cached and one of those products go out of stock all the other 99,999 products return a cache miss. Equally if a product is edited.

Please can you check. You will find that if you set a product qty to zero or change some such as title every single product, category, homepage, CMS page will result in a cache MISS.

Kind regards

[ahmed-midori]

Hi @engcom-Dash

Please could you check this issue again. You will be able to confirm by the additional information I have provided. Im sure with tis you will be able to confirm the issue.

Kind regards

[engcom-Dash]

Hi @ahmed-midori ,

Verified the issue in 2.4-develop instance and the issue is reproducible as per your last comment,Hence we are confirming the issue.

Kindly refer the below screenshots:




Following the change of qty to zero/out of stock :