Starting – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is initiated but encounters issues during startup. This could be due to insufficient memory, incorrect configuration settings, or a problem with the Elasticsearch version. To resolve this, ensure that your system has enough memory and disk space. Check your Elasticsearch configuration files for any errors or inconsistencies. Also, verify that you’re using a compatible version of Elasticsearch. If the problem persists, consider reinstalling Elasticsearch or seeking assistance from a professional.

This guide will help you check for common problems that cause the log ” starting … ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Log Context

Log “starting …” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    public Node start() throws NodeValidationException {
        if (lifecycle.moveToStarted() == false) {
            return this;
        }"starting ...");

        if (ReadinessService.enabled(environment)) {