Waiting until metadata writes are unblocked – 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 ” waiting until metadata writes are unblocked ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, plugin.

Log Context

Log “waiting until metadata writes are unblocked”classname  is LocalExporter.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

ClusterState clusterState = clusterService.state();
 if (clusterState.nodes().isLocalNodeElectedMaster()) {
 // we are on the elected master
 // Check that there is nothing that could block metadata updates
 if (clusterState.blocks().hasGlobalBlockWithLevel(ClusterBlockLevel.METADATA_WRITE)) {
 throw new ElasticsearchException("waiting until metadata writes are unblocked");
 // We haven't blocked off other resource installation from happening. That must be done first.
 assert migrationCoordinator.canInstall() == false : "migration attempted while resources could be erroneously installed";


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content