How To Solve Issues Related to Log – Unexpected token while reading snapshot metadata

How To Solve Issues Related to Log – Unexpected token while reading snapshot metadata

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 token while reading snapshot metadata” it’s important to understand a few problems related to Elasticsearch concepts blobstore, metadata, repositories, repository-azure, snapshot. See bellow important tips and explanations on these concepts

Log Context

Log”[{}] [{}] unexpected token while reading snapshot metadata [{}]” classname is BlobStoreRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         }
                    }
                    if (!ignoreIndexErrors) {
                        throw new ElasticsearchParseException("unexpected token  [" + token + "]");
                    } else {
                        logger.warn("[{}] [{}] unexpected token while reading snapshot metadata [{}]"; snapshotId; index; token);
                    }
                }
            } catch (IOException ex) {
                if (!ignoreIndexErrors) {
                    throw new SnapshotException(snapshotId; "failed to read metadata"; ex);




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 Caught Syntaxerror Unexpected Token  

Github Issue Number 12366  

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