When all retries are exhausted, the JDBC input plugin logs an errorUnable to execute statement. Tried #{@statement_retry_attempts} times. but does not raise an exception causing the pipeline to keep retrying in subsequent cron runs.
This is challenging from a monitoring perspective as I would rather have my readiness probe fail ASAP and not go through the deployment. So, I would like to request you to consider adding an option allowing users to fail the pipeline altogether if the input plugin has exhausted retries in any cron run.
When all retries are exhausted, the JDBC input plugin logs an error
Unable to execute statement. Tried #{@statement_retry_attempts} times.but does not raise an exception causing the pipeline to keep retrying in subsequent cron runs.This is challenging from a monitoring perspective as I would rather have my readiness probe fail ASAP and not go through the deployment. So, I would like to request you to consider adding an option allowing users to fail the pipeline altogether if the input plugin has exhausted retries in any cron run.