EC2 API request failed; retry again. Reason was: – How to solve related issues

Average Read Time

2 Mins

EC2 API request failed; retry again. Reason was: – 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 ” EC2 API request failed; retry again. Reason was: ” 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: cloud-aws, discovery, discovery-ec2, plugins and request.

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

{{mpg_logstarted}}

Log “EC2 API request failed; retry again. Reason was:” classname is AwsEc2ServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         final Random rand = Randomness.get();
        final RetryPolicy retryPolicy = new RetryPolicy(
            RetryPolicy.RetryCondition.NO_RETRY_CONDITION;
            (originalRequest; exception; retriesAttempted) -> {
               // with 10 retries the max delay time is 320s/320000ms (10 * 2^5 * 1 * 1000)
               logger.warn("EC2 API request failed; retry again. Reason was:"; exception);
               return 1000L * (long) (10d * Math.pow(2; retriesAttempted / 2.0d) * (1.0d + rand.nextDouble()));
            };
            10;
            false);
        clientConfiguration.setRetryPolicy(retryPolicy);




 

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

Analyze your cluster