|| at Jun 7, 2012 at 3:03 pm
Thanks Joey. Would it be as simple as...
1) Remove all components on all hosts (nn, snn, dn) per upgrade guide
2) Apply steps 1-5 on all hosts per upgrade guide
3) skip steps 6 thru 13?
3) Install/Upgrade to Cloudera Manager 4
4) Install to cluster as always?
On the upgrade page, we're stuck at step 6 - upgrade the hdfs metadata.
Since the hdfs-site.xml never had the dfs.name.dir, it defaults to the
file:/// then we get:
java.lang.IllegalArgumentException: Invalid URI for NameNode address (check
fs.defaultFS): file:/// has no authority.
Sorry to mix 2 issues into 1 thread. (upgrade if using CM plus exception on
On Thursday, June 7, 2012 10:50:37 AM UTC-4, Joey Echeverria wrote:
We probably need to make the docs around this better.
What you need to do is follow the steps from the CDH3 to CDH4 upgrade
guide that involve removing the CDH3 packages and installing the CDH4
packages. You don't have to worry about the config files in
/etc/<project> as those weren't being used and you dont' need to
install the packages that just contain service scripts (e.g.
I'll file a documentation JIRA to make the steps more clear.
On Thu, Jun 7, 2012 at 10:43 AM, Gary S wrote:
We used Cloudera Manager Free to install CDH3 in our cluster. Very simple.
We are trying to upgrade to CDH4 but it seems as though the instructions
I've found assume cdh3 was installed manually.
here for example. (back up old configs, make note of manual settings)
None of the config files on the hosts are configured manually since it was
all done through Cloudera Manager.
Can someone verify the steps? If I use the 13 steps to upgrade cdh3 to cdh4
then I wouldn't need Cloudera Manager in the first place.
And it's documentation here already says it won't upgrade cdh and to use the
Principal Solutions Architect