Skip to content
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

Default healthprobe values now causes max 120 seconds wait before backend is considered healthy #81

Open
fredvd opened this issue Oct 6, 2020 · 1 comment

Comments

@fredvd
Copy link
Member

fredvd commented Oct 6, 2020

@frisi You have added the healthprobe options to the recipe. Any reason why you changed the default Varnish settings from https://varnish-cache.org/docs/6.0/reference/vcl.html#probes in the recipe to have a default treshhold of 8?

The result is that when I restart a backend, it now takes 15s interval * 8 threshold = max 120 seconds before a restarted zope backend is considered healthy again. Varnish defaults to threshold 3, 45 seconds max.

@fredvd fredvd changed the title Default healthprobe values now causes max 120 seconds 503 errors before backend is considered healthyto switch a backend to healthy Default healthprobe values now causes max 120 seconds 503 errors before backend is considered healthy Oct 6, 2020
@fredvd fredvd changed the title Default healthprobe values now causes max 120 seconds 503 errors before backend is considered healthy Default healthprobe values now causes max 120 seconds wait before backend is considered healthy Oct 6, 2020
@frisi
Copy link
Member

frisi commented Oct 7, 2020

not 100% sure @fredvd

personally i use far lower values as my backend is a haproxy that handles timeouts of the zope instances (that take ~30/60 seconds until they can serve the first request)

health-probe-timeout = 2s
health-probe-interval = 5s
health-probe-window = 3
health-probe-threshold = 2

feel free to change/fix the defaults to whatever makes sense and whatever is considered the default setup for plone.recipe.varnish (i guess varnish in front of a zeo cluster)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants