Indexer cronjobs flushes all category and product pages in FPC / Varnish

[dverkade]

Preconditions

1. Magento 2.3.5-p1
2. Have Varnish configured as full page cache.
3. Have the Magento cronjob scheduled to run every minute.
4. Have the indexers all set to "Update on schedule"
5. Have Varnish configured to monitor / log incoming cache purge requests

Steps to reproduce

1. Have an indexer, for instance the "Category Products" index, set to "Index required"
2. Let the cronjob run every minute which will try to update the invalid indexes

Expected result

1. When the cron updating the indexes runs and it can't set the index to "Ready", don't flush the FPC for category and product pages.

Actual result

1. Magento sends a purge request to Varnish with the following tags: "cat_p" and "cat_c". This flushes all the category pages and product pages which are in the FPC, basically flushing the FPC every minute.

• 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 @dverkade. 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.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ihor-sviziev]

@dverkade could you add some example which request varnish gets?

[dverkade]

@ihor-sviziev example was already included in the initial description. The varnish request is including the following tags at this point: "cat_p" and "cat_c".

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[ihor-sviziev]

Hi @dverkade,
I understand the issue you have, but usually, when some data in the index has changed - we have to clean FPC for affected categories or products.
Do you have any thoughts on how we can implement your suggestion?

[dverkade]

Flushing of the caches could only occur when the index is set to "Ready" again. If the index fails flushing the caches should not occur.