Unexpected token – How to solve this Elasticsearch error

Average Read Time

2 Mins

Unexpected token – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” unexpected token ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: blobstore and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

Map globalCheckpoints = new HashMap();
  Map files = new HashMap();
  if (token == XContentParser.Token.START_OBJECT) {
  while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
  if (token != XContentParser.Token.FIELD_NAME) {
  throw new ElasticsearchParseException("unexpected token [{}]"; token);
  String currentFieldName = parser.currentName();
  token = parser.nextToken();
  if (token == XContentParser.Token.START_ARRAY) {
  if (ParseFields.FILES.match(currentFieldName; parser.getDeprecationHandler()) == false) {


Run the Check-Up to get a customized report like this:

Analyze your cluster