fluent / fluent/fluentd-forwarder

Problem on abrupt client disconnection

Open
#34 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
287
Forks
34
PR merge metrics
No merged PRs in 30d

Description

We've noticed that if a client suddenly terminates without cleanly closing the connection to fluentd-forwarder, then the forwarder starts to emit loads of messages like:

```
... temporary failure: read tcp from 127.0.0.1... An existing connection was forcibly closed by the remote host.
```

This happens on Windows.

Maybe [golang issue #6163](https://github.com/golang/go/issues/6163) and [this fix](https://go-review.googlesource.com/c/go/+/39490) could be related?

It would be nice if fluentd-forwarder was more resilient to abrupt client terminations.
Is there anything we can do on our side?

Thanks!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.