Member since
02-13-2014
11
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2936 | 07-14-2015 07:51 PM |
10-23-2015
01:06 PM
Awesome. Thank you.
... View more
10-23-2015
12:03 PM
Hi, instance type being used for the Manager is m3.medium and for the nodes I'm using m3.xlarge for all but Gateway, which also uses m3.medium. I've picked the Hadoop with Impala option with no customization. I've noticed CM is not accesible, so probably it haven't started. I'll take a look on that. Which instance type would you recommend for CM instead?
... View more
10-23-2015
11:51 AM
When building a new Cluster using Cloudera Director 1.5.1 it fails with the error: "API call to Cloudera Manager failed." I've experienced the problem 3 times in a row. First when creating Manager and Cluster at the same time, then 2 times when the Manager is already up and running. I haven't got any other error before this problem, which I'm guessing is one of the latest steps to have a working cluster. Stacktrace is below. ERROR [pipeline-thread-80] - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed
com.cloudera.api.ext.ClouderaManagerException: API call to Cloudera Manager failed. Method=ApiRootResource.getCurrentVersion, Args=null
at com.cloudera.api.ext.ClouderaManagerClientProxy.invoke(ClouderaManagerClientProxy.java:79) ~[launchpad-cloudera-manager-api-ext-1.5.1.jar!/:na]
at com.sun.proxy.$Proxy170.getCurrentVersion(Unknown Source) ~[na:na]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$HostInstall.run(BootstrapClouderaManagerAgent.java:145) ~[launchpad-bootstrap-1.5.1.jar!/:1.5.1]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$HostInstall.run(BootstrapClouderaManagerAgent.java:110) ~[launchpad-bootstrap-1.5.1.jar!/:1.5.1]
at com.cloudera.launchpad.pipeline.job.Job3.runUnchecked(Job3.java:32) ~[launchpad-pipeline-1.5.1.jar!/:1.5.1]
at com.cloudera.launchpad.pipeline.job.Job3$$FastClassBySpringCGLIB$$54178503.invoke(<generated>) ~[spring-core-4.1.5.RELEASE.jar!/:1.5.1]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:97) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at com.cloudera.launchpad.pipeline.PipelineJobProfiler$1.call(PipelineJobProfiler.java:55) ~[launchpad-pipeline-1.5.1.jar!/:1.5.1]
at com.codahale.metrics.Timer.time(Timer.java:101) ~[metrics-core-3.1.0.jar!/:3.1.0]
at com.cloudera.launchpad.pipeline.PipelineJobProfiler.profileJobRun(PipelineJobProfiler.java:51) ~[launchpad-pipeline-1.5.1.jar!/:1.5.1]
at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_65]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_65]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$HostInstall$$EnhancerBySpringCGLIB$$a9863238.runUnchecked(<generated>) ~[spring-core-4.1.5.RELEASE.jar!/:1.5.1]
at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:165) [launchpad-pipeline-1.5.1.jar!/:1.5.1]
at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:136) [launchpad-pipeline-1.5.1.jar!/:1.5.1]
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:98) [launchpad-pipeline-1.5.1.jar!/:1.5.1]
at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.run(DatabasePipelineRunner.java:120) [launchpad-pipeline-database-1.5.1.jar!/:1.5.1]
at com.cloudera.launchpad.ExceptionHandlingRunnable.run(ExceptionHandlingRunnable.java:57) [launchpad-common-1.5.1.jar!/:1.5.1]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
... View more
Labels:
- Labels:
-
Cloudera Manager
07-14-2015
07:51 PM
I've managed to solve the issue by adding the configuration directive below to the cloudera-manager section. repository: "http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.4.3/"
... View more
07-14-2015
11:57 AM
Hi, I've downloaded Cloudera Director 1.1.3. After configuring the environment for my cluster at AWS I've faced a tricky issue. Everything went fine until the point of installing Cloudera Manager. Checking the log I've noticed that even though CD has picked the right version for CM (5.4.3) when the package manager tries to download the RPM (I'm using RHEL 6) it tries to use a former version directory (5.3.3), then it fails because the RPM for 5.4.3 is not present there, of course. Has anybody faced such situation? I'm guessing the YUM .repo is the problem. Any hints? Logs are below. [2015-07-14 04:18:15] INFO [io-thread-1] - ssh:10.0.0.64: ---> Package cloudera-manager-daemons.x86_64 0:5.4.3-1.cm543.p0.258.el6 will be installed [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: --> Finished Dependency Resolution [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Dependencies Resolved [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: ================================================================================ [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Package Arch Version Repository Size [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: ================================================================================ [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Installing: [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: cloudera-manager-daemons [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: x86_64 5.4.3-1.cm543.p0.258.el6 cloudera-manager 638 M [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Transaction Summary [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: ================================================================================ [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Install 1 Package(s) [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Total download size: 638 M [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Installed size: 902 M [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Downloading Packages: [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.3.3/RPMS/x86_64/cloudera-manager-daemons-5.4.3-1.cm543.p0.258.el6.x86_64.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found” [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Trying other mirror. [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: Error Downloading Packages: [2015-07-14 04:18:16] INFO [io-thread-1] - ssh:10.0.0.64: cloudera-manager-daemons-5.4.3-1.cm543.p0.258.el6.x86_64: failure: RPMS/x86_64/cloudera-manager-daemons-5.4.3-1.cm543.p0.258.el6.x86_64.rpm from cloudera-manager: [Errno 256] No more mirrors to try.
... View more
Labels:
- Labels:
-
Cloudera Manager