Auto-follow pattern is missing – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch’s Cross-Cluster Replication (CCR) feature is used and the auto-follow pattern is not correctly set up or missing. The auto-follow pattern is essential for automatically replicating indices from a leader to a follower cluster. To resolve this issue, ensure that the auto-follow pattern is correctly configured in the CCR settings. Check the syntax and the naming conventions. Also, verify that the leader cluster is accessible and the necessary permissions for replication are granted.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” auto-follow pattern [{}] is missing ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “auto-follow pattern [{}] is missing” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 AutoFollowMetadata autoFollowMetadata = metadata.custom(AutoFollowMetadata.TYPE);
 if (autoFollowMetadata == null) {
 if (name == null) {
 return Collections.emptyMap();
 } else {
 throw new ResourceNotFoundException("auto-follow pattern [{}] is missing"; name);
 }  if (name == null) {
 return autoFollowMetadata.getPatterns();


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?