Bug #16217
closed
[arvados-ws] Websocket server stops processing events, but stays connected
Added by Tom Clegg over 4 years ago.
Updated about 4 years ago.
Release relationship:
Auto
Description
Sometimes, after successfully processing hundreds or thousands of events, arvados-ws goes into a state where clients don't receive any events. The EventsIn number at /status.json is static, which indicates arvados-ws isn't receiving events from PostgreSQL.
Clients can still connect / stay connected, the once-per-minute empty "ping" message still works.
Cause is unknown.
- Target version set to 2020-03-25 Sprint
- Assigned To set to Tom Clegg
- Status changed from New to In Progress
Not sure whether this is related to the observed failures but it seems worth fixing either way. Arvados-ws does a periodic listener ping, but hasn't been checking the returned error. With this change, if the ping fails, arvados-ws will log the error and exit/restart.
16217-ws-ping @ 9ebf73b1a1229bba507057ed2fb6a39635ce7e24 -- developer-run-tests: #1765
16217-ws-ping LGTM, thanks!
- Target version changed from 2020-03-25 Sprint to 2020-04-08 Sprint
- Status changed from In Progress to Resolved
Also available in: Atom
PDF