Closed TimQSO closed 5 years ago
Hi @GuiltyNL. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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-engcom-team give me 2.3-develop instance
- upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@GuiltyNL do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @engcom-backlog-nazar. 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:
[ ] 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.3-develop
branchDetails
- Add the comment @magento-engcom-team give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop
branch. Details
- Add the comment @magento-engcom-team give me 2.2-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop
branch, please add the label Reproduced on 2.2.x
Next steps are available in case you are a member of Community Maintainers.
[ ] 6. Add label Issue: Confirmed
once verification is complete.
[ ] 7. Make sure that automatic system confirms that report has been added to the backlog.
@magento-engcom-team Yes, this has been reproduced on a vanilla Magento instance.
Hi @GuiltyNL thank you for you report, i;m not able to reproduce following steps you described on clean 2.3-develop instance.
@GuiltyNL: How are your indexers setup, as Updated by Schedule
or Update on Save
?
I remember a talk from @johnhughes1984 at MM19NL saying there is a bug in Magento when the latter is chosen in that it always flushes the entire cache instead of only flushing the cache specific to a certain product/category.
Hi @hostep indexers are updated by schedule.
Also the FPC always changes to 'INVALIDATED' after a (short) while.
The cache is also completely flushed after a customer places an order. And sometimes that is every few minutes. So our shop is uncached most of the time.
Our cache warmer tries to keep up and warms about 1.200.000 pages per day because of the constant flushing.
Hi GuiltyNL Did you find a solution to this ?
thanks
Yes, our developers wrote a fix, it has something to do with the anchors in the 'Top Menu' because of that everything was chained together and everything was flushed.
Hi There
Thanks for getting back. It would be a great help if you could point me to your developers as we have a similar problem and we are at a total loss about this.
Your help is much appreciated.
Kind Regards Hemant
From: GuiltyNL notifications@github.com Sent: Friday, 10 July 2020 1:25 AM To: magento/magento2 magento2@noreply.github.com Cc: vnsinfo hemant@vnsinfo.com.au; Comment comment@noreply.github.com Subject: Re: [magento/magento2] Magento FPC get flushed completely when changing category or adding a new product. (#21385)
Yes, our developers wrote a fix, it has something to do with the anchors in the 'Top Menu' because of that everything was chained together and everything was flushed.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/21385#issuecomment-656193213 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AG66BJ3R545JAI7IUZ45BALR2XOM3ANCNFSM4GY6PDCA . https://github.com/notifications/beacon/AG66BJ2VBPJ4N3U77DY7OSTR2XOM3A5CNFSM4GY6PDCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE4OLNPI.gif
hi @GuiltyNL,
I'm facing the same issue, I truly appreciate if you can share the fix.
Thank You
*Preconditions ()**
*Steps to reproduce ()**
*Expected result ()**
*Actual result ()**
Note. The page cache is being flushed to aggressive. Pages that haven't been changed are removed from the cache while this is unneeded. It causes that a site alsmost doesn't server pages from FPC and when you use a cache warmer, this warmer isn't able to keep up on busy e-commerce sites.
When flushing like this, almost every Magento 2 store has an almost empty FPC, which is a bit akward.