Member since
05-18-2015
8
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4401 | 07-10-2017 11:56 PM |
07-10-2019
03:30 AM
I am using Cloudera Express 5.12.0 in a test environment. I want to upgrade to a later release. How do we do this? All of the Cloudera documentation seems to have removed any mention of Express edition. Is there no longer a free option? If there is where is it?
... View more
08-15-2017
05:22 AM
My cluster is all configured and managed with Cloudera Express. I am trying to run a new job on accumulo and get this error. Caused by: java.io.IOException: Cannot initialize Cluster. Please check your configuration for mapreduce.framework.name and the correspond server addresses.
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:120)
at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1267)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1263)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1692)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1262)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1291)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1315) Any clues on how to troubleshoot?
... View more
Labels:
- Labels:
-
Apache Accumulo
-
MapReduce
07-10-2017
11:56 PM
2 Kudos
Thanks very much for replying. I was hoping these forums might be a bit busier but I guess there aren't so many people using community edition these days. Anyway, I did get this working in the end, but I was very disappointed in the lack of clear documentation. From what I remember this is what I did: **BACKUP NAMENODE BEFORE TOUCHING ANYTHING** 1) Shutdown the cluster 2) Upgraded to 5.11 using Parcels in CM. Did *NOT* restart cluster 3) Started ZooKeepers only 4) Went to HDFS and choose "Upgrade HDFS Metadata". The new binaries must be in place, and the cluster must be down 5) Then try to finalize the upgrade. I am not sure this worked as expected. I think there was an issue with one BP 6) re-started cluster 7) When to NameNode page and selected "Finalize Metadata Upgrade" After a long time it all sorted itself out and is up and running on 5.11 What a painful process though.
... View more
07-10-2017
11:59 AM
I can not do this from the command line because the packages aren't installed with yum. eg; sudo service hadoop-hdfs-namenode upgrade Does not work I can not do this with Cloudera Manager Express because rolling restart is not supported. So, catch-22. Do I give up on Cloudera Manager and go back to a manual configuration? Surely this is possible??
... View more
07-10-2017
09:44 AM
I use Cloudera Manager Express. I am trying to upgrade from 5.3.8 to 5.11.1 When I use CME I get an error: "File system image contains an old layout version -59. An upgrade to version -60 is required." As CME does not support rolling restart I will need to do this manually. Can anyone point me to documentation on how to do a rolling restart from the command line because CME does not support it. Thanks Paul
... View more
Labels:
- Labels:
-
Cloudera Manager