Policy does not exist – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” policy does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “policy [{}] does not exist”classname  is EnrichPolicyExecutor.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public void runPolicyLocally(ExecuteEnrichPolicyTask task; String policyName; ActionListener listener) {
 try {
 EnrichPolicy policy = EnrichStore.getPolicy(policyName; clusterService.state());
 if (policy == null) {
 throw new ResourceNotFoundException("policy [{}] does not exist"; policyName);
 task.setStatus(new ExecuteEnrichPolicyStatus(ExecuteEnrichPolicyStatus.PolicyPhases.SCHEDULED));
 Runnable runnable = createPolicyRunner(policyName; policy; task; listener);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content