Failure caught – How to solve related issues

Average Read Time

2 Mins

Failure caught – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failure caught ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: bulk.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “failure caught” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         public void exceptionCaught(ChannelHandlerContext ctx; ExceptionEvent e) throws Exception {
            if (e.getCause() instanceof BindException) {
                // ignore; this happens when we retry binding to several ports; its fine if we fail...
            logger.warn("failure caught"; e.getCause());

    class BulkListener implements BulkProcessor.Listener {


Run the Check-Up to get a customized report like this:

Analyze your cluster