Restoring quantiles for job job getId – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch attempts to restore quantiles for a machine learning job with a specific ID, but encounters an issue. This could be due to a problem with the snapshot from which it’s trying to restore, or the job ID might not exist. To resolve this, ensure the snapshot is valid and the job ID exists. If the snapshot is corrupted, you may need to create a new one. If the job ID doesn’t exist, check for any typographical errors or create a new job with the correct ID.

This guide will help you check for common problems that cause the log ” Restoring quantiles for job ‘” + job.getId() + “‘ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Restoring quantiles for job ‘” + job.getId() + “‘” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        return "--maxAnomalyRecords=" + MAX_ANOMALY_RECORDS_SETTING_DYNAMIC.get(settings);

    private void buildQuantiles(List command) throws IOException {
        if (quantiles != null && quantiles.getQuantileState().isEmpty() == false) {
  "Restoring quantiles for job '" + job.getId() + "'");

            Path normalizersStateFilePath = writeNormalizerInitState(job.getId(); quantiles.getQuantileState(); env);

            String quantilesStateFileArg = QUANTILES_STATE_PATH_ARG + normalizersStateFilePath;


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?