Unexpected error during the primary phase for action ; request – 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 ” Unexpected error during the primary phase for action ; request ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: replication and request.

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 “unexpected error during the primary phase for action [{}]; request [{}]” classname is TransportReplicationAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 assert false : "finishAsFailed called but operation is already finished";
            }
        }

        void finishWithUnexpectedFailure(Throwable failure) {
            logger.warn("unexpected error during the primary phase for action [{}]; request [{}]"; failure; actionName; request);
            if (finished.compareAndSet(false; true)) {
                setPhase(task; "failed");
                listener.onFailure(failure);
            } else {
                assert false : "finishWithUnexpectedFailure called but operation is already finished";




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content