Member since
06-17-2014
17
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2771 | 10-12-2015 02:53 AM |
03-14-2016
03:18 AM
Hi Cloudera team, I'm using CM 5.3.0 and have a question about Oozie. Do you know if its possible to disable some steps from a Oozie workflow ? For example I have a workflow with step1, step2, step3, step4, step5 and in the first execution the step1, step2 and step3 are success, and step4, and step5 failed When I want to start the second execution of the workflow, is normal to want to run only the failed steps, namely step4 and step5. I didn't find any options from Hue/Oozie interface and also Google didn't helped me. Thanks, Tudor
... View more
Labels:
- Labels:
-
Apache Oozie
-
Cloudera Hue
-
Cloudera Manager
10-19-2015
04:56 AM
Hi guys, I started to read the cloudera documenation how to upgrade Cloudera Manager : http://www.cloudera.com/content/www/en-us/documentation/enterprise/5-3-x/topics/cm_ag_upgrade_cm5.html#concept_qjq_cxz_zn_unique_2 This is how CM can be installed : Installation Path A - Automated Installation by Cloudera Manager Installation Path B - Manual Installation Using Cloudera Manager Packages Installation Path C - Manual Installation Using Cloudera Manager Tarballs Right now I have Cloudera Manager 5.3.0 and installed in using Path A. I want to upgrade it to latest CM, but in the upgrade documentation I have this : " Choose a procedure based on how you installed Cloudera Manager: Upgrade Cloudera Manager Server (Packages) Install Cloudera Manager Server and Agent Software (Tarballs) " The upgrade documentation doesn't include the way I installed the CM (and I think the most popular one). How did you upgrade your CM if you installed it using the automated way ? Thanks, Tudor
... View more
Labels:
- Labels:
-
Cloudera Manager
-
Manual Installation
10-12-2015
02:53 AM
Hi again Gautam, in the end I managed to manually install Cloudera Manager 5.3.0. The problem was caused on by the previous manual install of Cloudera Manager 5.4.7. I made a full cleanup of my server, using this instructions : "http://www.cloudera.com/content/cloudera/en/documentation/cloudera-manager/v5-1-x/Cloudera-Manager-Installation-Guide/cm5ig_uninstall_cm.html" and know it works. Thanks for your interest, Tudor
... View more
10-12-2015
01:09 AM
Hi Gautam, thanks for your replay. I have this error when I want to start Cloudera Manager Server using command "sudo service cloudera-scm-server start" . So, I don't have access to http://ip_cloudera_server:7180. I would like to know where to specify the property "latest_supported" CDH version, taking in consideration that I can't access http://ip_cloudera_server:7180. My first guess is that I have to specify it into the embeded postgress database, but I didn't find how until now. Thank, Tudor
... View more
10-09-2015
08:04 AM
Hi all, I'm tring to install Cloudera Manager 5.3.0. I'm using the embaded postgress database. When I start the cloudera server, I receive the following error in its log file : 2015-10-09 17:35:57,593 INFO main:com.cloudera.cmon.TimeSeriesEntityType: Registered TimeSeriesEntityType HDFS_CACHE_DIRECTIVE 2015-10-09 17:35:57,605 INFO main:com.cloudera.cmon.MetricSchema: Schema json: jar:file:/usr/share/cmf/lib/server-5.3.0.jar!/com/cloudera/cmon/schema.json 2015-10-09 17:35:57,645 WARN ParcelUpdateService:com.cloudera.cmf.persist.ReadWriteDatabaseTaskCallable: Error while executing CmfEntityManager task java.lang.IllegalArgumentException: Illegal character in path at index 41: http://archive.cloudera.com/cdh5/parcels/{latest_supported}/manifest.json at java.net.URI.create(URI.java:859) at com.ning.http.client.RequestBuilderBase.buildUrl(RequestBuilderBase.java:343) at com.ning.http.client.RequestBuilderBase.setUrl(RequestBuilderBase.java:328) at com.ning.http.client.AsyncHttpClient$BoundRequestBuilder.setUrl(AsyncHttpClient.java:336) at com.ning.http.client.AsyncHttpClient.requestBuilder(AsyncHttpClient.java:589) at com.ning.http.client.AsyncHttpClient.prepareGet(AsyncHttpClient.java:425) at com.cloudera.parcel.components.ParcelDownloaderImpl.prepareGet(ParcelDownloaderImpl.java:558) at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfoFuture(ParcelDownloaderImpl.java:511) at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfo(ParcelDownloaderImpl.java:469) at com.cloudera.parcel.components.ParcelDownloaderImpl.syncRemoteRepos(ParcelDownloaderImpl.java:339) at com.cloudera.parcel.components.ParcelDownloaderImpl$1.run(ParcelDownloaderImpl.java:409) at com.cloudera.parcel.components.ParcelDownloaderImpl$1.run(ParcelDownloaderImpl.java:404) at com.cloudera.cmf.persist.ReadWriteDatabaseTaskCallable.call(ReadWriteDatabaseTaskCallable.java:36) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.URISyntaxException: Illegal character in path at index 41: http://archive.cloudera.com/cdh5/parcels/{latest_supported}/manifest.json at java.net.URI$Parser.fail(URI.java:2829) at java.net.URI$Parser.checkChars(URI.java:3002) at java.net.URI$Parser.parseHierarchical(URI.java:3086) at java.net.URI$Parser.parse(URI.java:3034) at java.net.URI.<init>(URI.java:595) at java.net.URI.create(URI.java:857) ... 16 more I assume that I have to specify somewhere the latest_supported property, but I don't know where. I tried also to install the current Cloudera Manager (5.4.7) and it works perfectly. Do you have any suggestions to solve the problem ? Thanks, Tudor
... View more
Labels:
- Labels:
-
Cloudera Manager