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] [Updated] (AMBARI-11306) RU to copy correct version of tarball, including tez.tar.gz and mapreduce.tar.gz
Date Fri, 22 May 2015 03:11:17 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-11306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-11306:
-----------------------------------------
    Attachment: AMBARI-11306.patch

> RU to copy correct version of tarball, including tez.tar.gz and mapreduce.tar.gz
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-11306
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11306
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11306.patch
>
>
> We copy tarballs to HDFS in several places. The problem is that during Resource Manager
Start in RU it copies 
> /usr/hdp/current/tez-client/lib/tez.tar.gz to hdfs:///hdp/apps/{{ hdp_stack_version }}/tez/
> for the hdp_stack_version value that comes from running "hdp-select status hadoop-yarn-resourcemanager".
> So the destination is correct (uses the "to" version), but the source is incorrect because
the tez-client symlink is still pointing to the older version, since tez-client only switches
to the newer version when the Clients are upgraded, which occurs later during the orchestration.
> The fix is that during RU, the source location of the tarballs must be /usr/hdp/{{ hdp_version
}}/component/tarball.tar.gz
> where {{ hdp_version }} is the version going to.
> Another problem is that during RU, HiveServer2 Start is not copying mapreduce.tar.gz
tarball to HDFS. In this Jira, we should also clean up the tarball source and destination
variables to come from a file instead of configs in cluster-env.



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

Mime
View raw message