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

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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();
    }





 

Run the Check-Up to get a customized report like this:

Analyze your cluster