Reply
Highlighted
New Contributor
Posts: 2
Registered: ‎08-09-2017
Accepted Solution

Cloudera Director failing in aws

Hi,

 

While installing cloudera manager via cloudera director , i am facing the below error.

 

Can anyone please help.

[2018-09-20 02:47:26.206 +0000] WARN [p-233d83a21bfb-DefaultBootstrapDeploymentJob] 0d6b540d-642f-42f3-81c2-e305d1c0661d POST /api/v12/environments/Dev/depl
oyments com.cloudera.launchpad.bootstrap.AllocateInstances$AllocateAndWaitForInstancesToRun - c.c.l.bootstrap.AllocateInstances: Error while attempting to al
locate instances for group CM. Attempting to continue.
com.cloudera.launchpad.pipeline.UnrecoverablePipelineError: Problem allocating on-demand instances
at com.cloudera.launchpad.pluggable.common.ExceptionConditions.propagateWithSuppressedDetails(ExceptionConditions.java:126)
at com.cloudera.launchpad.pluggable.compute.PluggableComputeProvider.allocate(PluggableComputeProvider.java:616)
at com.cloudera.launchpad.pluggable.compute.PluggableComputeProvider.allocateInstancesForTemplate(PluggableComputeProvider.java:545)
at com.cloudera.launchpad.pluggable.compute.PluggableComputeProvider.allocate(PluggableComputeProvider.java:520)
at com.cloudera.launchpad.pluggable.compute.PluggableComputeProvider.allocate(PluggableComputeProvider.java:331)
at com.cloudera.launchpad.bootstrap.AllocateInstances$AllocateAndWaitForInstancesToRun.run(AllocateInstances.java:221)
at com.cloudera.launchpad.bootstrap.AllocateInstances$AllocateAndWaitForInstancesToRun.run(AllocateInstances.java:196)
at com.cloudera.launchpad.pipeline.job.Job2.runUnchecked(Job2.java:31)
at com.cloudera.launchpad.pipeline.job.Job2$$FastClassBySpringCGLIB$$54178502.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
at com.cloudera.launchpad.pipeline.PipelineJobProfiler.profileJobRun(PipelineJobProfiler.java:60)
at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.aspectj.AbstractAspectJAdvic


Suppressed: com.cloudera.launchpad.pluggable.common.ExceptionConditions$DetailHolderException: Exception details:
key: null
PluginExceptionCondition{type=ERROR, exceptionInfo={message=Encountered AWS exception, awsErrorCode=InvalidParameterValue, awsErrorMessage=Duplicate tag key 'Name' specified.}}

Caused by: com.cloudera.director.spi.v2.model.exception.UnrecoverableProviderException: Problem allocating on-demand instances
at com.cloudera.director.aws.AWSExceptions.propagate(AWSExceptions.java:121)
at com.cloudera.director.aws.ec2.EC2Provider.allocateOnDemandInstances(EC2Provider.java:1513)
at com.cloudera.director.aws.ec2.EC2Provider.allocate(EC2Provider.java:742)
at com.cloudera.director.aws.ec2.EC2Provider.allocate(EC2Provider.java:1)
at com.cloudera.launchpad.pluggable.compute.PluggableComputeProvider.allocate(PluggableComputeProvider.java:614)
... 36 common frames omitted
[2018-09-20 02:47:26.206 +0000] ERROR [p-233d83a21bfb-DefaultBootstrapDeploymentJob] 0d6b540d-642f-42f3-81c2-e305d1c0661d POST /api/v12/environments/Dev/deployments com.cloudera.launchpad.bootstrap.AllocateInstances$AllocateAndWaitForInstancesToRun - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed
com.cloudera.launchpad.pipeline.UnrecoverablePipelineError: Insufficient number of instances available after allocation

 

 

With regards,

Avinash P

Master
Posts: 305
Registered: ‎07-01-2015

Re: Cloudera Director failing in aws

You have the explanation probably on the last line of the error message. Try to request the soft limits for the number of instances.
New Contributor
Posts: 2
Registered: ‎08-09-2017

Re: Cloudera Director failing in aws

HiAll,

 

Actually i was doing mistake with the Tag , i removed them and it is working fine now.

 

Thanks All,

Avinash P

Cloudera Employee
Posts: 74
Registered: ‎10-28-2014

Re: Cloudera Director failing in aws

I think that this log line highlights the error.

 

PluginExceptionCondition{type=ERROR, exceptionInfo={message=Encountered AWS exception, awsErrorCode=InvalidParameterValue, awsErrorMessage=Duplicate tag key 'Name' specified.}}

 

Are you trying to add a "Name" tag to your instances? Cloudera Altus Director uses the "Name" tag, but can be re-configured to use a different tag instead. See https://www.cloudera.com/documentation/director/latest/topics/director_aws_custom_tag_names.html for instructions on how to do so.

 

Announcements