How To Solve Issues Related to Log – Failed to properly stop client thread

How To Solve Issues Related to Log – Failed to properly stop client thread

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Failed to properly stop client thread” it’s important to understand a few problems related to Elasticsearch concepts client, index, reindex, thread. See bellow important tips and explanations on these concepts

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



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Elasticsearch Rest Client Still Giving IOException : Too Many Open Files 3.81 K 6

Elasticsearch unclosed client. Live threads after Tomcat shutdown. Memory usage impact?   0.49 K -

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now