Open elevinskii opened 1 month ago
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@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
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: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. 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
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12884 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
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
indexer_reindex_all_invalid
cron job to fail every time (throw an exception in the job).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