Skip to content

ping/pong the upstream websocket server #73

@haardikk21

Description

@haardikk21

With the cloudflare outage today, we noticed that the RPC node stopped receiving messages from upstream. Root cause seemed to be a broken TCP pipe where the node believed the connection was still established, but it was in fact not established - and it got stuck waiting for messages to come from upstream and therefore stopped processing flashblocks

The websocket proxy already ping/pongs the clients, so likely the proxy disconnected the node - but the node didn't get the disconnection message either and continued to believe it was still connected. Simply restarting the node to force a reconnection fixed the issue (after Cloudflare was relatively healthy)

We should add ping/pong going from Node -> Proxy as well, not just Proxy -> Node to ensure we can force a reconnection.

Metadata

Metadata

Assignees

Labels

F-bugFlag: Something isn't workingM-good-first-issueMeta: Good for newcomers

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions