[jira] [Created] (AMBARI-10821) Ambari stack upgrade HDP 2.2.0.0 => 2.2.4.2 does not update /usr/hdp/current to correct stack version for unmanaged/unused components

["Hari Sekhon (JIRA)" <ji...@apache.org>]

Hari Sekhon created AMBARI-10821:
------------------------------------

             Summary: Ambari stack upgrade HDP 2.2.0.0 => 2.2.4.2 does not update /usr/hdp/current to correct stack version for unmanaged/unused components
                 Key: AMBARI-10821
                 URL: https://issues.apache.org/jira/browse/AMBARI-10821
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.0.0
         Environment: HDP 2.2.0.0 => HDP 2.2.4.2
            Reporter: Hari Sekhon
            Priority: Trivial


After upgrading the HDP stack from 2.2.0.0 => HDP 2.2.4.2 many of the /usr/hdp/current symlinks are not updated to the new stack version.

On further investigation it appears that services that are not deployed on given nodes are not updated to the new stack. This could cause some unexpected results where people are running client code from the wrong version assuming that hdp current should point to the currently deployed stack or when manually starting services that Ambari is not managing such as hadoop-hdfs-nfs3 (which we are using for example). What's strange is that some components that are not managed were upgraded to the correct stack version such as spark-client, which I'm not about to move in to being managed and yet it's hdp current link was upgraded (perhaps because it didn't exist before).

Below is a unique list of link mappings across all nodes colated to show the divergence of different nodes:
{code}accumulo-gc -> /usr/hdp/2.2.0.0-2041/accumulo
accumulo-master -> /usr/hdp/2.2.0.0-2041/accumulo
accumulo-monitor -> /usr/hdp/2.2.0.0-2041/accumulo
accumulo-tablet -> /usr/hdp/2.2.0.0-2041/accumulo
accumulo-tracer -> /usr/hdp/2.2.0.0-2041/accumulo
falcon-client -> /usr/hdp/2.2.0.0-2041/falcon
falcon-server -> /usr/hdp/2.2.0.0-2041/falcon
flume-server -> /usr/hdp/2.2.0.0-2041/flume
hadoop-client -> /usr/hdp/2.2.4.2-2/hadoop
hadoop-hdfs-client -> /usr/hdp/2.2.4.2-2/hadoop-hdfs
hadoop-hdfs-datanode -> /usr/hdp/2.2.4.2-2/hadoop-hdfs
hadoop-hdfs-journalnode -> /usr/hdp/2.2.0.0-2041/hadoop-hdfs
hadoop-hdfs-journalnode -> /usr/hdp/2.2.4.2-2/hadoop-hdfs
hadoop-hdfs-namenode -> /usr/hdp/2.2.0.0-2041/hadoop-hdfs
hadoop-hdfs-namenode -> /usr/hdp/2.2.4.2-2/hadoop-hdfs
hadoop-hdfs-nfs3 -> /usr/hdp/2.2.0.0-2041/hadoop-hdfs
hadoop-hdfs-portmap -> /usr/hdp/2.2.0.0-2041/hadoop-hdfs
hadoop-hdfs-secondarynamenode -> /usr/hdp/2.2.0.0-2041/hadoop-hdfs
hadoop-httpfs -> /usr/hdp/2.2.4.2-2/hadoop-httpfs
hadoop-mapreduce-client -> /usr/hdp/2.2.4.2-2/hadoop-mapreduce
hadoop-mapreduce-historyserver -> /usr/hdp/2.2.0.0-2041/hadoop-mapreduce
hadoop-mapreduce-historyserver -> /usr/hdp/2.2.4.2-2/hadoop-mapreduce
hadoop-yarn-client -> /usr/hdp/2.2.4.2-2/hadoop-yarn
hadoop-yarn-nodemanager -> /usr/hdp/2.2.4.2-2/hadoop-yarn
hadoop-yarn-resourcemanager -> /usr/hdp/2.2.0.0-2041/hadoop-yarn
hadoop-yarn-resourcemanager -> /usr/hdp/2.2.4.2-2/hadoop-yarn
hadoop-yarn-timelineserver -> /usr/hdp/2.2.0.0-2041/hadoop-yarn
hbase-client -> /usr/hdp/2.2.0.0-2041/hbase
hbase-master -> /usr/hdp/2.2.0.0-2041/hbase
hbase-regionserver -> /usr/hdp/2.2.0.0-2041/hbase
hive-client -> /usr/hdp/2.2.4.2-2/hive
hive-metastore -> /usr/hdp/2.2.0.0-2041/hive
hive-metastore -> /usr/hdp/2.2.4.2-2/hive
hive-server2 -> /usr/hdp/2.2.0.0-2041/hive
hive-server2 -> /usr/hdp/2.2.4.2-2/hive
hive-webhcat -> /usr/hdp/2.2.0.0-2041/hive-hcatalog
hive-webhcat -> /usr/hdp/2.2.4.2-2/hive-hcatalog
kafka-broker -> /usr/hdp/2.2.0.0-2041/kafka
kafka-broker -> /usr/hdp/2.2.4.2-2/kafka
knox-server -> /usr/hdp/2.2.0.0-2041/knox
mahout-client -> /usr/hdp/2.2.0.0-2041/mahout
oozie-client -> /usr/hdp/2.2.4.2-2/oozie
oozie-server -> /usr/hdp/2.2.0.0-2041/oozie
oozie-server -> /usr/hdp/2.2.4.2-2/oozie
phoenix-client -> /usr/hdp/2.2.0.0-2041/phoenix
pig-client -> /usr/hdp/2.2.4.2-2/pig
ranger-admin -> /usr/hdp/2.2.0.0-2041/ranger-admin
ranger-usersync -> /usr/hdp/2.2.0.0-2041/ranger-usersync
slider-client -> /usr/hdp/2.2.0.0-2041/slider
spark-client -> /usr/hdp/2.2.4.2-2/spark
sqoop-client -> /usr/hdp/2.2.4.2-2/sqoop
sqoop-server -> /usr/hdp/2.2.0.0-2041/sqoop
storm-client -> /usr/hdp/2.2.0.0-2041/storm
storm-nimbus -> /usr/hdp/2.2.0.0-2041/storm
storm-slider-client -> /usr/hdp/2.2.0.0-2041/storm-slider-client
storm-supervisor -> /usr/hdp/2.2.0.0-2041/storm
tez-client -> /usr/hdp/2.2.4.2-2/tez
zookeeper-client -> /usr/hdp/2.2.4.2-2/zookeeper
zookeeper-server -> /usr/hdp/2.2.0.0-2041/zookeeper
zookeeper-server -> /usr/hdp/2.2.4.2-2/zookeeper{code}
The fix is trivial to hdp-select yourself for each one but it would be nice if Ambari kept everything cleanly on the right version to avoid surprises like this.

Hari Sekhon
http://www.linkedin.com/in/harisekhon



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)