Is there a way to handle JDBC input failures so that the main Logstash pipeline does not not stop and restart every time an error is thrown by one input ?
Probably not, but what behavior would you prefer? What kind of JDBC failures are you having?
We have multiple JDBCs pointed at different Databases and occasionally one of those databases may not be available resulting in SQL(e.g tcp/ip connection to the host failed) errors being thrown by the input and crashing the main pipeline. I'd like to be able to handle the error in someway so as the main pipeline continues to run and does its work with the other jdbc inputs.
That's probably not possible today, but I think it sounds like a bug. A transient connection problem should be dealt with in a graceful manner.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.