How To Solve Issues Related to Log – Unexpected error during the primary phase for action

How To Solve Issues Related to Log – Unexpected error during the primary phase for action

Updated: Feb-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 “Unexpected error during the primary phase for action” it’s important to understand a few problems related to Elasticsearch concepts replication, shard. See bellow important tips and explanations on these concepts

Log Context

Log”unexpected error during the primary phase for action [{}]” classname is TransportShardReplicationOperationAction.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 [{}]"; failure; actionName);
            if (finished.compareAndSet(false; true)) {
                Releasables.close(indexShardReference);
                listener.onFailure(failure);
            } else {
                assert false : "finishWithUnexpectedFailure called but operation is already finished";




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 Primary Index Randomly Getting Dele  

Unable To Create The Index  

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