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] [Commented] (AMBARI-11039) RU wrong version of tez.tar.gz uploaded to HDFS
Date Sat, 09 May 2015 02:09:00 GMT

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

Alejandro Fernandez commented on AMBARI-11039:
----------------------------------------------

There will be separate Jira to fix this in 2.1.0

> RU wrong version of tez.tar.gz uploaded to HDFS
> -----------------------------------------------
>
>                 Key: AMBARI-11039
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11039
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.1
>
>
> Summary: Customers with Ambari 2.0.0 that performed an RU from say HDP 2.2.0.0 to 2.2.4.2
will not have the correct version of tez.tar.gz uploaded to HDFS.
> Details: During HiveServer2 Restart in RU, it copied to wrong tez.tar.gz to HDFS (because
the symlink in /usr/hdp/current/tez is still pointing to the old version at this time).
> The reason why Service Checks pass is that these tarballs are compatible enough with
each other. However, during RU from 2.2.* to 2.3.*, this is likely to break.
> Impact: Applications that depend on this tarball (Pig, Tez, Hive) will be running with
older classes. This does not appear to be breaking in HDP 2.2, otherwise customers would have
reported it. However, it certainly does have to be fixed in Ambari 2.1.0 because tez.tar.gz
has more significant changes and does encounter a version incompatibility error.



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

Mime
View raw message