ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-7825) Rolling Upgrades - hdfs:///apps/tez/tez.tar.gz needs to be versioned
Date Fri, 17 Oct 2014 04:44:33 GMT


Hadoop QA commented on AMBARI-7825:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:


Test results:
Console output:

This message is automatically generated.

> Rolling Upgrades - hdfs:///apps/tez/tez.tar.gz needs to be versioned
> --------------------------------------------------------------------
>                 Key: AMBARI-7825
>                 URL:
>             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, 2.0.0
>         Attachments: AMBARI-7825.patch
> *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 and 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 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-

This message was sent by Atlassian JIRA

View raw message