Open Mugen1991 opened 6 years ago
@Mugen1991 - the WARN messages are very noisy from the underlying library. IMO, many of those WARN should be DEBUG since as far as I can tell are fairly normal and routine for lease acquirement for the distribution of nodes. In testing I have seen these alot, and never had any of the WARN messages warrant much attention. (unless you don't see any data, then a misconfiguration like a typo in the connection string is usually hidden in noisy the WARN logs).
However, that ERROR message is new. In testing, I could never get this error to actually fire. It also appears that the logging is incorrect for the error. I have corrected the logging for the error in 1.0.1 that may shed more light on what that ERROR was logged.
bin/logstash-plugin update logstash-input-azure_event_hubs
I'm hitting this with an ERROR logged as well. When I run a plugin update, I get the following:
Updating logstash-input-azure_event_hubs
No plugin updated
Events do seem to flow for a while before getting this error.
I am currently running 3 Logstash instances for a couple of eventhubs. Every now and then I get the following errors. Is there some parameter to prevent this ? Does this mean, i will have duplicate events or lost events?