-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Purge from magento wrong behaviour #153
Comments
This is odd; I have to admit that I'm not particularly familiar with Magento, and their recommended Varnish setup. Since you've asked about a shared volume: No, there shouldn't be any special setup necessary. From your issue, I infer that you're already using the Signaller component to broadcast PURGE requests to your cluster members, and that these signals are in fact received by the members. Could you share how you run your purge request specifically, and also the part of your VCL configuration (reminder: don't know a thing about Magento) that handles the purge requests? |
Yes sure, I make the purge from the admin of magento, and from the cli of magento with a command, and when I change a product or something in the admin panel magento do a purge. I can see the purge well in logs in the 2 pods, but the change is cached about 5 mins when I have 2 pods. The vcl config is: `vclTemplate: |
The logs of purge received in same time to 2 pods of varnish, pod1 : `* << Request >> 1183468
and pod 2 `* << Request >> 496589
Thx so much |
I have 2 pods of httpcache and 2 pods of magento and when purge I can see the signal in the 2 pods of httpcache, but I can't see the changes until after a few minutes, when they are automatically updated. When only have 1 pod of httpcache I can see the changes instantly. do you know why?
I have the vcl config recommended by magento. Need share a volume or a special vcl config for use 2 pods of httpcache?
Regards.
The text was updated successfully, but these errors were encountered: