Log Requested shutdown of indexer for job – How To Solve Related Issues

Log Requested shutdown of indexer for job – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Requested shutdown of indexer for job” it’s important to understand a few problems related to Elasticsearch concepts indexer, indexing, plugin. See bellow important tips and explanations on these concepts

Log Context

Log”Requested shutdown of indexer for job [“ classname is AsyncTwoPhaseIndexer.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        case STOPPED:
            return false;

        case ABORTING:
            logger.info("Requested shutdown of indexer for job [" + getJobId() + "]");
            onAbort();
            return false;

        default:
            // Anything other than indexing; aborting or stopping is unanticipated




 

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 How to stop

91.96 K 75

Elasticsearch Java High Level REST Client Establish A Bunch of TCP Connection and Don’t Close that Connections After Putting Data

  1.42 K 7

 

About Opster

Opster provides real-time recommendations to resolve and prevent Elasticsearch problems and can perform advanced actions that improve performance, automate operation and reduces costs

Find Configuration Errors

Analyze Now