ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-7825) Rolling Upgrades - hdfs:///apps/tez/tez.tar.gz needs to be versioned
Date Fri, 17 Oct 2014 03:47:34 GMT
Alejandro Fernandez created AMBARI-7825:
-------------------------------------------

             Summary: Rolling Upgrades - hdfs:///apps/tez/tez.tar.gz needs to be versioned
                 Key: AMBARI-7825
                 URL: https://issues.apache.org/jira/browse/AMBARI-7825
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 1.7.0
            Reporter: Alejandro Fernandez
            Assignee: Alejandro Fernandez
            Priority: Blocker
             Fix For: 1.7.0


*HDP 2.2 using versioned RPMs*
When Ambari installs Hive, it copies any file that matches /usr/hdp/current/tez-client/lib/tez*.tar.gz
file to hdfs:///apps/tez/tez.tar.gz
(Aside: it also ends up copying other tez-* files that it shouldn't because they are not needed,
and already zipped in the tar.gz file)

The problem is that during a rolling upgrade, currently running jobs still needs to reference
the same jar files as when they were created.

Today, Hive's install_jars.py and params.py route /usr/hdp/current/tez-client/lib/tez*.tar.gz
=> tez.tar.gz

Instead, it should preserve the version number when copying to HDFS.

Further, when tez.py generates the tez-site.xml file, it should replace the value of the tez.lib.uris
parameter to include the rpm version number in the value, e.g., hdfs:////apps/tez/tez-0.6.0.2.2.0.0-887.tar.gz



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

Mime
View raw message