-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Logstash 2.4 Filebeat 1.3. Logstash stops sending data after a couple of days because of too many socket connections #6300
Comments
@elpibeperez I will take a look, I wonder if the thread are not blocked on something. A few questions:
|
Curiously we don't see this issue on v2.3.4 but do on v2.4.1 with the beats input. beats: |
I think the following is happening the |
Okay, I think we might be tracking 2 differents things. I've noticed the following, when the
Theses state will stay like this forever and the socket wont be freed, since the connection is sane and no network errors has happened. My hypothessis, since filebeat is not activelly reading the socket when it doesn't have to send anything no I believe your problem is related to that scenario but let me ask a few questions to really get to the bottom of this story.
|
I've release a new version of beats 3.1.12 that should fix this issue, you can upgrade your plugin with the following command:
Edit: Update instead of upgrade. |
Thank you guys. We are trying this out. |
It's |
Logstash configuration:
After two days of running Logstash it can't send any more messages because beats opened too many connections (Beats eventually die because it is autoscaled).
Beats communication with logstashs consumes all the server sockets. It does not close the sockets after an inactivity of 15 seconds as it says it would
The text was updated successfully, but these errors were encountered: