Fatal error in thread ; exiting – How to solve related issues

Fatal error in thread ; exiting – How to solve related issues

Opster Team

Jan-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 ” Fatal error in thread ; exiting ” 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: bootstrap, handler and thread.

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 “Fatal error in thread [{}]; exiting” classname is ElasticsearchUncaughtExceptionHandler.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     static boolean isFatalUncaught(Throwable e) {
        return e instanceof Error;
    }

    void onFatalUncaught(final String threadName; final Throwable t) {
        logger.error(() -> new ParameterizedMessage("fatal error in thread [{}]; exiting"; threadName); t);
    }

    void onNonFatalUncaught(final String threadName; final Throwable t) {
        logger.warn(() -> new ParameterizedMessage("uncaught exception in thread [{}]"; threadName); t);
    }




 

Run the Check-Up to get customized recommendations like this:

error

The high disk watermark threshold is about to be reached in specific nodes

error-img

Description

There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…

error-img

Recommendations

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized code snippet to resolve the issue]

Optimize Elasticsearch Performance

Run The Tool