You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've not yet looked into the health check itself. If we determine that the health check should be used, we need to ensure that we modify this from /pub/health_check.php to /health_check.php, as we have Nginx configured to use /pub as the document root for PHP files.
The text was updated successfully, but these errors were encountered:
What if a client is running Magento AND a non-Magento site with a different hostname, and the non-Magento site is also using Varnish? We'd need to ensure the health check file exists on the other site, and that such a file is actually relevant to that site.
If the defined backend (within the VCL file) is HAProxy, HAProxy will forward that to a "random" server, and Varnish is not aware of that. Varnish would need to be configured with multiple backends instead, otherwise, we risk Varnish thinking the backend is down when it may only be one server. I suppose it would be possible to do away with HAProxy altogether, define multiple backends in the VCL, and update the VCL on an interval instead of the HAProxy config. We'd need to do some testing on the impact of reloading Varnish
https://github.com/jetrails/magento2-varnish/blob/master/Helper/VclGenerator.php#L155
Currently, we are commenting out most lines in the backend definition/array. In particular, we may want to consider using the health check:
I've not yet looked into the health check itself. If we determine that the health check should be used, we need to ensure that we modify this from
/pub/health_check.php
to/health_check.php
, as we have Nginx configured to use/pub
as the document root for PHP files.The text was updated successfully, but these errors were encountered: