Error while listing local files resetting the starting sequence number from – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.1

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch encounters an issue while trying to list local files, causing it to reset the starting sequence number. This could be due to file corruption, insufficient permissions, or a disk space issue. To resolve this, you could try checking the file integrity, ensuring OpenSearch has the necessary permissions to access the files, or freeing up disk space. Additionally, you might want to check the OpenSearch logs for more detailed error information.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” error while listing local files; resetting the starting sequence number from {} ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: indices, recovery.

Log Context

Log “error while listing local files; resetting the starting sequence number from {}” classname is PeerRecoveryTargetService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

            assert startingSeqNo == UNASSIGNED_SEQ_NO : startingSeqNo;
            logger.trace("{} shard folder empty; recovering all files"; recoveryTarget);
            metadataSnapshot = Store.MetadataSnapshot.EMPTY;
        } catch (final IOException e) {
            if (startingSeqNo != UNASSIGNED_SEQ_NO) {
                logger.warn(new ParameterizedMessage("error while listing local files; resetting the starting sequence number from {} " +
                    "to unassigned and recovering as if there are none"; startingSeqNo); e);
                startingSeqNo = UNASSIGNED_SEQ_NO;
            } else {
                logger.warn("error while listing local files; recovering as if there are none"; e);
            }

 

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?

Get expert answers on Elasticsearch/OpenSearch