Indexer deferred cache's not being flushed by commit or nesting issue

[elevinskii]

Preconditions and environment

Magento 2.4.6-p6

Cron jobs, responsible for reindexing tasks, are primarily using DeferredCacheContext for collecting tags and entities for cache flushing and further process them later at once.

The cache context object has an internal pointer of nesting, and pushes registered tags/entities only if the pointer is equal to 1. That's understandable, having nesting hierarchy logics, only last commit must take the action.

What will happen if some of cron jobs finish erroneously with doing start and incrementing the level pointer but never commiting?

Steps to reproduce

1. Make indexer_reindex_all_invalid cron job to fail every time (throw an exception in the job).
2. Do some changes in a products to put them to partial reindex queue.
3. Keep an eye what cache tags have been invalidated in the var/log/cache.log after cron runs.

Expected result

Every product/related categories tags, such as cat_p_*, cat_c_* are pushed for invalidation.

Actual result

No cache tags are invalidated by partial cron reindex.

Additional information

No response

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 @elevinskii. 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-Hotel. 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-Hotel]

Hello @elevinskii,

Thanks for the report and collaboration!

We have gone through the DeferredCacheContext class and we agree with your point. Hence we are confirming the issue for further processing.

Thanks