Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR o.f.logger.sender.RawSocketSender - org.fluentd.logger.sender.RawSocketSender java.net.SocketException: Connection timed out (Write failed) #54

Open
Einsteinl opened this issue Sep 7, 2020 · 2 comments

Comments

@Einsteinl
Copy link

In my use case, we can not assume that fluentd will always be running. Ideally, the logger would log as usual if fluentd is running; if it is not running, it should probably log a warning and move on instead of throwing exceptions; finally, it should silently try to reconnect in the background and resume logging as soon as a connection is available.

Ideally the library would also do some in-memory buffering to minimize loss of log msgs. Thoughts?

@sndyuk
Copy link
Owner

sndyuk commented Oct 1, 2020

@Einsteinl Yes, it should be so. I'll check it.

@sndyuk
Copy link
Owner

sndyuk commented Oct 3, 2020

@Einsteinl You can use fluency for the time being which has the retry feature.
fluentd-logger doesn't have the retry feature but the feature must be needed on logback-more-appenders. I will implement it when I have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants