GraphQl Schema Is Not Cached With Redis

[m08110071]

Preconditions and environment

• Magento 2.4.7-p2
• Redis 7.2 and config requirepass
• Config redis for cache and specific cache prefix id
• Enable all cache types

Steps to reproduce

• Call any GraphQl query and debug to file: vendor/magento/framework/Config/Data.php:108

Expected result

GraphQl schema is cached

Actual result

GraphQl schema is not cached

Additional information

1. I tried to debug and see this issue happen since below code added:

File: vendor/magento/module-catalog-graph-ql/etc/di.xml

<virtualType name="Magento\Framework\GraphQl\Config\Data" type="Magento\Framework\Config\Data"> <arguments> <argument name="cacheTags" xsi:type="array"> <!-- Note: Because of DynamicAttributeReaders, this cache needs to be cleaned when attributes change--> <item name="EAV" xsi:type="string">EAV</item> </argument> </arguments> </virtualType>

2. Some cases, cache is stored to file automatically

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 @m08110071. 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.

[m08110071]

@engcom-Bravo This is my PR to fix It:
#39172

[m2-assistant]

Hi @engcom-November. 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!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @m08110071,

Thank you for the report and collaboration!

Not able to reproduce this on 2.4-develop with redis cache configured.
When calling the graphql query second time, the cacheId is being cached.

Please take a look at the screenshot below:

And also the same key can be seen in redis as well:

Please let us know if we are missing anything.

Thank you.