Closed davidread closed 1 year ago
RM just experienced this:
this has just happened to me right now, in case it is useful for you to see an example in progress. I was just viewing an array and scrolling down through it when it disconnected. I tried to view the array again and got a 503 error in the console. I refreshed and got a 503 in the browser.
The pod shows some events. He flagged it happening 10 minutes ago, so the second one is most relevant:
Warning Unhealthy 16m kubelet, ip-192-168-10-250.eu-west-1.compute.internal Liveness probe failed: Get http://100.96.49.15:3000/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 11m kubelet, ip-192-168-10-250.eu-west-1.compute.internal Readiness probe failed: Get http://100.96.49.15:8787/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
We found that the node went bad briefly - NodeNotReady. So the 11 people with R Studio on this node suffered a short period of outage at this time. This would manifest as 503 and connection errors, as described.
So that's the explanation. Sorry about the disruption. We'll look at what we can do to prevent this in future.
CG is suffering this in R Studio:![connection](https://user-images.githubusercontent.com/307612/62204598-09e81780-b37d-11e9-9e1e-bd09b003f0c6.png)
Related:
This user is working on DOM1.
It might be due to flaky home wifi? Is a serious issue for this user.