Failed to get metadata for placement/availability-zone – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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: discovery, discovery-ec2, metadata and Plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Failed to get metadata for [placement/availability-zone]” classname is Ec2DiscoveryPlugin.java.
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);
        }

        return attrs.build();
    }





 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content