-
Notifications
You must be signed in to change notification settings - Fork 26
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
RabbitMQ output plugin blocks logstash to start if server is down #37
Comments
I can confirm that this is happening with our system as well.Our system is set up as the following: We have many different N number of pipelines that have this: pipeline-N.conf:
and then we have a single rabbitmq pipeline that is setup like this:
Assume the "***" is actual values. The error occurs in this use-case:
At this point, logstash is correctly dealing with the packets being sent to it (sending to elastic in our case and not sending to rabbitmq for obvious reasons). But the really strange thing is that the logstash HTTP API is completely unreachable. Once rabbit gets turned back on the logstash HTTP API works fine again and we can get the health. So it definitely seems to be related to the initial rabbitmq connection breaking thats somehow relating to the logstash http server being blocked or crashing? My (only slightly) educated guess is that this might have something to do with March Hare and Faraday? Anyways, this is causing a lot of problems for us and our only solution is to us an older version of the logstash output plugin with our own fixes to catch the connection breaking. But again this is less than ideal since a lot of changes have happened since and we would rather just use the built in plugin to avoid more unnecessary in-house fixes. |
today, I confirm that it is still an open problem :( it's a really annoying problem that causing a lot of problems :( |
I put my hands in the code and I solved the bug (YES, it is a BUG and it's not so hard to fix it, very few changes are needed). At the moment I need some more test, but after this I try to submit code :) |
Ho really good new! Many thanks 👍
Le sam. 23 avr. 2022 à 23:40, Massimiliano Dal Cero <
***@***.***> a écrit :
… I put my hands in the code and I solved (it's not so hard, very few
changes are needed). At the moment I need some more test, but after this I
try to submit code :)
—
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJJZ2JU3IC3HPGAI47K3VLVGRU23ANCNFSM4SKCE6MQ>
.
You are receiving this because you authored the thread.Message ID:
<logstash-plugins/logstash-integration-rabbitmq/issues/37/1107653464@
github.com>
|
is absurd that the official developers do not fix this :( but mainly, how did they not notice it? ... probably, perhaps, they never did any test in a real evinronment :(
|
We run logstash, with RabbitMQ output, and our RabbitMQ server is down. Logstash never start properly (I mean, HTTP API is not started), looks like it stucks at plugin registration, so I suspect the connection inside register method, to prevent Logstash to start, is that possible?
If so, what about lazy connect to RabbitMQ server, when the 1st event comes?
Our use case:
(Reference > elastic/logstash#12330)
The text was updated successfully, but these errors were encountered: