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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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.

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



 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content