Failed to get metadata for placement availability-zone – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve metadata for a specific placement availability zone. This could be due to network issues, incorrect configuration, or issues with the cloud service provider. To resolve this, you can check your network connectivity, verify your Elasticsearch configuration settings, or contact your cloud service provider to ensure there are no issues on their end. Additionally, ensure that the specified availability zone exists and is accessible.

This guide will help you check for common problems that cause the log ” failed to get metadata for [placement/availability-zone] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, plugins, discovery, discovery-ec2.

Log Context

Log “failed to get metadata for [placement/availability-zone]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            } else {
                attrs.put(Node.NODE_ATTRIBUTES.getKey() + "aws_availability_zone"; metadataResult);
        } catch (final IOException e) {
            // this is lenient so the plugin does not fail when installed outside of ec2
            logger.error("failed to get metadata for [placement/availability-zone]"; e);



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?