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

Nginx front-end proxy does not check that back-end omero-web is alive #78

Open
manics opened this issue Jan 29, 2018 · 2 comments
Open

Comments

@manics
Copy link
Contributor

manics commented Jan 29, 2018

Haproxy connects to Nginx on idr-omeroreadonly-N which is always running even if OMERO.web is unavailable (e.g. during a restart). We should figure out a proper liveness check e.g. check the HTTP status code from Nginx

@manics manics changed the title haproxy does not check that omero-web is alive Nginx front-end proxy does not check that back-end omero-web is alive Mar 8, 2018
@manics
Copy link
Contributor Author

manics commented Mar 8, 2018

Correction: It's a front-end nginx and not haproxy that connects to the backends. The open-source Nginx does not seem to support HTTP status-based checks: https://docs.nginx.com/nginx/admin-guide/load-balancer/http-health-check/

I think we should replace it with haproxy.

@manics
Copy link
Contributor Author

manics commented Mar 8, 2018

An addition benefit is we could use cookie based session pinning instead of by IP/24 (another limitation of the open-source Nginx)

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

1 participant