Unexpected error during the primary phase for action ; request – How to solve related issues

Average Read Time

2 Mins

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. 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: replication and request.

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

{{mpg_logstarted}}

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";




 

Run the Check-Up to get a customized report like this:

Analyze your cluster