Skip to content

Metrics servers not killed on connection delete (ID mismatch) #429

Description

@ravjotbrar

When deleting a connection in Electron mode, the server fails to shut down the associated metrics server process. The console logs "Could not kill metrics server process" for each node.

closeMetricsServer in connection.ts sends the full connectionId (127-0-0-1-7000-db0) in the POST body to /connection/close, but the metrics process compares against its own ownNodeId (127-0-0-1-7000). The mismatch causes the metrics process to reject the request with 400.

Metrics server processes accumulate as orphans after connections are deleted. They continue running, consuming memory and holding Valkey connections until the app is fully quit.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions