Failed to properly stop client thread – 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 ” Failed to properly stop client thread ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: client, index, reindex and thread.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Failed to properly stop client thread [{}]” classname is TransportReindexAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             super.finishHim(failure; indexingFailures; searchFailures; timedOut);
            // A little extra paranoia so we log something if we leave any threads running
            for (Thread thread : createdThreads) {
                if (thread.isAlive()) {
                    assert false: "Failed to properly stop client thread [" + thread.getName() + "]";
                    logger.error("Failed to properly stop client thread [{}]"; thread.getName());
                }
            }
        }

        
Override



 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content