You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2015/04/03 05:59:52 UTC

[jira] [Updated] (TEZ-2270) TezClient.create() with AM localresources CLASSPATH order (Rolling Upgrade)

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

Gopal V updated TEZ-2270:
-------------------------
    Summary: TezClient.create() with AM localresources CLASSPATH order (Rolling Upgrade)  (was: TezClient.create() with AM localresources CLASSPATH order)

> TezClient.create() with AM localresources CLASSPATH order (Rolling Upgrade)
> ---------------------------------------------------------------------------
>
>                 Key: TEZ-2270
>                 URL: https://issues.apache.org/jira/browse/TEZ-2270
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Gopal V
>
> When a Tez AM is started with a LocalResource which is also present on the cluster, the added JAR should be preferred to the cluster version (during rolling upgrades).
> Running a different version on an existing cluster results shows incompatibilities triggered by the fact that the tez.tar.gz files are ahead of the cluster classpath, while the LocalResources are added after the cluster classpath.
> Mixing the order up results in the user-added JAR being ineffective in forcing the client version over the cluster version.



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