[ 
https://issues.apache.org/jira/browse/AMBARI-11306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555497#comment-14555497
 ] 

Hadoop QA commented on AMBARI-11306:
------------------------------------

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

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2817//console

This message is automatically generated.

> 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
>
>
> 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)

Reply via email to