Price cached on the Redis server.

[drew7721]

Preconditions (*)

1. Magento 2.3.2 and above
2. Need to have multiple instances that have independent Redis servers on each instance.
3. Say using something similar to this https://devdocs.magento.com/common/images/cloud_stack-diagram.png

Steps to reproduce (*)

1. Change a product price.
2. Only the Redis cache on the admin instance will be flushed, not the Redis caches on the other instances.

Expected result (*)

1. Flush caches on all redis instances like it's done for varnish.

Actual result (*)

1. The price does not change on all instances.

This was introduced by this commit 1d9b1ba and all the other commits related to it.
Based on the commit message it's fixing some MC-6273 issue that has to do with the queries to the url_rewrite table. Don't see how the commit message is relevant with the code changes.

I really don't see the need to cache the product price_box html once more in Redis when we have the full_page cache for that.

How many layers of caching are needed?

Instead of fixing bugs caused by caches such as #3625 this is now adding more caches that will just cause more issues down the line.

[m2-assistant]

Hi @drew7721. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@drew7721 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[drew7721]

To reproduce this you need an environment that runs multiple instances of the code and the Redis cache server.

[danemacmillan]

After doing a bit more research into this, I found the commit that is responsible for this problem:

#19897

I also commented about the problem this introduces:

#19897 (comment)

[m2-assistant]

Hi @drew7721. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[ihor-sviziev]

Hi @drew7721 @danemacmillan,
As I understood - you have own redis server on each web node? If so - it's wrong configuration as the web nodes not shares the cache that leads to higher load on each node and issues like you described above.

Could you explain more your use case?