-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Incident] m2lines hub unavailable for a short period of time #1248
Comments
Looking at logs with
|
Looking at previous hub logs to that (via https://cloudlogging.app.goo.gl/eodshAcsprGxppAp8), I see:
This started around So it looks like the k8s master was dead for those times, but somehow this also affected the proxy / nginx - otherwise, only the hub itself is supposed to be unavailable when the k8s master is dead. |
Similar set of log error messages around the same time in the proxy
|
@rabernat do you know which page gave you 'service unavailable'? Was it the hub home page or the specific notebook you were on? |
This just bumps up the priority of #1102 - that makes the k8s master far more robust (at some cost), but probably worth it here. |
Less prone to k8s API failure this way, although it costs about 70$ a month Ref 2i2c-org#1248 Ref 2i2c-org#1102
Less prone to k8s API failure this way, although it costs about 70$ a month Ref 2i2c-org#1248 Ref 2i2c-org#1102
Fixed by #1251 |
Summary
From https://2i2c.freshdesk.com/a/tickets/125
Impact on users
Important information
Tasks and updates
After-action report template
The text was updated successfully, but these errors were encountered: