influxdata / influxdata/kapacitor

Occasional errors when .post()'ing alert to an HTTP server

Open
#686 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

In a percentage of times (5-40%), we get a Connection reset error on the HTTP server that receives the POST request from the alert node. We handle the alert just fine so this is not critical, but it seems that the connection is closed before it gets a chance to reply.

CAUSE: java.net.SocketException: Connection reset

The exception is thrown when attempting to write a response to the socket. The response is usually sent within 1ms of receiving the POST request. Is there some configurable timeout or intentional reason why we'd reset the connection so soon?

Contributor guide

Open the contributing guide

Research direction

The issue names no repository files or tests. Start by reproducing the alert node's HTTP POST against a server that reports the connection reset, then trace the request and response handling; done means identifying the cause of the premature reset and confirming a reliable response or documented configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.