Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

CD cluster suspend failure

Highlighted

CD cluster suspend failure

New Contributor

Dear All,

 

I am exploring CD vmware SPI to deploy in the vmware vpshere enviorment, where my I am vcenter server version 6.5 and esxi 6.6 with two boxes.

 

My CD is 2.2.1 and CM version

Cloudera Enterprise Data Hub Edition Trial 5.7.2 (#17 built by jenkins on 20160722-1347 git: 1ac5976e8ad8f16506c2db236aee83141915c44d)

Java VM Name: Java HotSpot(TM) 64-Bit Server VM

Java VM Vendor: Oracle Corporation

Java Version: 1.7.0_80

 

In the last step of Cluster deployment i getting failure... i have attached the error message for your reference, looking for help....

 

 

[2017-02-22 04:03:50] ERROR [pipeline-thread-54] - c.c.l.p.DatabasePipelineRunner: Pipeline ea81e01f-fd74-470f-859d-15e4fa418928 suspended due to failure
com.cloudera.api.ext.ClouderaManagerException: API call to Cloudera Manager failed. Method=ParcelResource.startDistributionCommand
    at com.cloudera.api.ext.ClouderaManagerClientProxy.invoke(ClouderaManagerClientProxy.java:97) ~[launchpad-cloudera-manager-api-ext-2.1.0.jar!/:2.1.0]
    at com.sun.proxy.$Proxy225.startDistributionCommand(Unknown Source) ~[na:na]
    at com.cloudera.launchpad.bootstrap.cluster.DistributeParcel.runCommand(DistributeParcel.java:159) ~[launchpad-bootstrap-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.bootstrap.cluster.ParcelStageTransitionJob.run(ParcelStageTransitionJob.java:95) ~[launchpad-bootstrap-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.bootstrap.cluster.ParcelStageTransitionJob.run(ParcelStageTransitionJob.java:36) ~[launchpad-bootstrap-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.pipeline.job.Job4.runUnchecked(Job4.java:33) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.pipeline.job.Job4$$FastClassBySpringCGLIB$$54178504.invoke(<generated>) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:97) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at com.cloudera.launchpad.pipeline.PipelineJobProfiler$1.call(PipelineJobProfiler.java:67) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at com.codahale.metrics.Timer.time(Timer.java:101) ~[metrics-core-3.1.2.jar!/:3.1.2]
    at com.cloudera.launchpad.pipeline.PipelineJobProfiler.profileJobRun(PipelineJobProfiler.java:63) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at sun.reflect.GeneratedMethodAccessor180.invoke(Unknown Source) ~[na:na]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_91]
    at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_91]
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
    at com.cloudera.launchpad.bootstrap.cluster.DistributeParcel$$EnhancerBySpringCGLIB$$9044e242.runUnchecked(<generated>) ~[launchpad-bootstrap-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:159) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:130) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at com.github.rholder.retry.AttemptTimeLimiters$NoAttemptTimeLimit.call(AttemptTimeLimiters.java:78) ~[guava-retrying-1.0.6.jar!/:na]
    at com.github.rholder.retry.Retryer.call(Retryer.java:110) ~[guava-retrying-1.0.6.jar!/:na]
    at com.cloudera.launchpad.pipeline.util.PipelineRunner.attemptMultipleJobExecutionsWithRetries(PipelineRunner.java:99) ~[launchpad-pipeline-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.run(DatabasePipelineRunner.java:125) ~[launchpad-pipeline-database-2.1.0.jar!/:2.1.0]
    at com.cloudera.launchpad.ExceptionHandlingRunnable.run(ExceptionHandlingRunnable.java:57) [launchpad-common-2.1.0.jar!/:2.1.0]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_91]
    at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_91]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_91]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_91]
    at java.lang.Thread.run(Thread.java:745) [na:1.7.0_91]
[2017-02-22 04:03:50] ERROR [pipeline-thread-54] - c.c.l.p.DatabasePipelineRunner: Pipeline 'ea81e01f-fd74-470f-859d-15e4fa418928' failed
    at com.cloudera.launchpad.bootstrap.cluster.DistributeParcel$$EnhancerBySpringCGLIB$$9044e242
    at com.cloudera.launchpad.bootstrap.cluster.EnableParcels:1

[2017-02-22 04:03:50] INFO  [pipeline-thread-54] - c.c.l.p.s.PipelineRepositoryService: Pipeline 'ea81e01f-fd74-470f-859d-15e4fa418928': RUNNING -> SUSPENDED
[2017-02-22 04:03:50] INFO  [pipeline-thread-54] - c.c.l.d.ClusterRepositoryService: Cluster 'Cluster1': BOOTSTRAPPING -> BOOTSTRAP_FAILED

 

Kind Regards,

YogaT

 

1 REPLY 1

Re: CD cluster suspend failure

Expert Contributor

YogaT,

 

You'll have to look in the CM server logs for information on why the API request from Director to CM failed.

 

This information is likely only included in the CM server logs if the "enable_api_debug" flag is set to true. You can set this in the conf file as shown in the aws.reference.conf. You can also set this through the CM UI if you are deploying the cluster against a CM that has already been bootstrapped.

 

David