02-15-2017 11:38 AM
We upgraded our clusters from 5.5.2 to 5.5.5 a while ago. We've since identified a few nodes where the alternatives are still referencing the 5.5.2 parcel.
root@use542ytb9:~ ( use542ytb9 ) 13:15:15 $ which hbase /usr/bin/which: no hbase in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/sbin:/usr/sbin:/usr/local/sbin:/root/bin) root@use542ytb9:~ ( use542ytb9 )
root@use542ytb9:~ ( use542ytb9 ) 13:15:18 $ ls /usr/bin/hbase /usr/bin/hbase root@use542ytb9:~ ( use542ytb9 ) 13:15:24 $ ll /usr/bin/hbase lrwxrwxrwx 1 root root 23 May 16 2016 /usr/bin/hbase -> /etc/alternatives/hbase root@use542ytb9:~ ( use542ytb9 ) 13:15:28 $ ll /etc/alternatives/hbase lrwxrwxrwx 1 root root 63 May 16 2016 /etc/alternatives/hbase -> /opt/cloudera/parcels/CDH-5.5.2-1.cdh5.5.2.p1426.1277/bin/hbase root@use542ytb9:~ ( use542ytb9 ) 13:15:30 $ ls /opt/cloudera/parcels/CDH-5.5.2-1.cdh5.5.2.p1426.1277/bin/hbase ls: cannot access /opt/cloudera/parcels/CDH-5.5.2-1.cdh5.5.2.p1426.1277/bin/hbase: No such file or directory root@use542ytb9:~ ( use542ytb9 )
We've cycled the cm agent, done full decommissions and recommisisons, rebooted the nodes, and deployed client config.
Since we've identified 3 nodes, we're assuming there's others as well. The hadoop services still run on these nodes, but we're unable to run hdfs, hbase, or yarn commands, which has also caused several mapreduce jobs to fail.
Is there a good way to repoint these alternatives to the new parcel?
02-15-2017 12:51 PM
which link that you have followed for the upgrade?
As per the above link, there is no intermediate version between 5.5.4 and 5.6.0 (But you are referring to 5.5.5 ?)
02-15-2017 01:01 PM
03-13-2017 07:27 AM