Random_score seed must be an int; long or string; not ‘ – How to solve this Elasticsearch error

Random_score seed must be an int; long or string; not ‘ – 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 ” random_score seed must be an int; long or string; not ‘ ” 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: long, query 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”random_score seed must be an int; long or string; not ‘”classname  is RandomScoreFunctionBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.numberType() == XContentParser.NumberType.INT) {
  randomScoreFunctionBuilder.seed(parser.intValue());
  } else if (parser.numberType() == XContentParser.NumberType.LONG) {
  randomScoreFunctionBuilder.seed(parser.longValue());
  } else {
  throw new ParsingException(parser.getTokenLocation(); "random_score seed must be an int; long or string; not '"
  + token.toString() + "'");
  }
  } else if (token == XContentParser.Token.VALUE_STRING) {
  randomScoreFunctionBuilder.seed(parser.text());
  } else {

 

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

Analyze your cluster