How To Solve Issues Related to Log – No ec2 metadata returned from

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check-Up

Last update: Feb-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 


Troubleshooting background

To troubleshoot Elasticsearch log “No ec2 metadata returned from” it’s important to know common problems related to Elasticsearch concepts: cloud-aws, discovery-ec2, metadata, node, plugins. See below-detailed explanations complete with common problems, examples and useful tips.

Metadata in Elasticsearch

What it is

Metadata is information about the data. In Elasticsearch, each document has associated metadata such as _id and _index meta fields.

Examples
  • Routing meta field:
    • _routing, a routing value that places a document in a particular shard.
  • Other meta field
    • _meta, not used by Elasticsearch but can be used to store application-specific metadata.
PUT index_01
{
  "mappings": {
    "_meta": { 
      "class": "App01::User01",
      "version": "01"
    }
  }
}

  • Identity meta fields: 
    _id , the id of the document, for example querying based on _id field
PUT index01/_doc/1
{
  "text": "Document with ID 1"
}
 
PUT index01/_doc/2
{
  "text": "Document with ID 2"
}
 
GET index01/_search
{
  "query": {
    "terms": {
      "_id": [ "1", "2" ] 
    }
  }
}


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1. Filter out metadata fields and only return source fields in elasticsearch – Stats : ♥ 21.04 K  Ι √ 29

2. S Instance Metadata For Iam Is Not      


Log Context

Log ”No ec2 metadata returned from” classname is Ec2CustomNodeAttributes.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

             in = urlConnection.getInputStream();
            BufferedReader urlReader = new BufferedReader(new InputStreamReader(in; StandardCharsets.UTF_8));

            String metadataResult = urlReader.readLine();
            if (metadataResult == null || metadataResult.length() == 0) {
                logger.error("no ec2 metadata returned from {}"; url);
                return null;
            }
            ec2Attributes.put("aws_availability_zone"; metadataResult);
        } catch (IOException e) {
            logger.debug("failed to get metadata for [placement/availability-zone]"; e);






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?