%s %s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch’s status is set to “S s”, which means it’s in a “shard started” state. This is not an error but a status message indicating that a shard has been successfully started. However, if you’re experiencing issues, it could be due to a misconfiguration or a problem with the cluster’s health. To resolve this, ensure that your cluster is properly configured, check the health of your cluster, and ensure that all nodes are functioning correctly. If the problem persists, consider reindexing your data or increasing the number of shards.

This guide will help you check for common problems that cause the log ” [%s] %s ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: replication.

Log Context

Log “[%s] %s” classname is TransportWriteAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            String message;
            Exception exception;
            ActionListener listener
        ) {
            if (TransportActions.isShardNotAvailableException(exception) == false) {
                logger.warn(() -> format("[%s] %s"; replica.shardId(); message); exception);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?