[jira] [Commented] (TEZ-1664) Add checks to ensure that the client and AM are compatible

["Bikas Saha (JIRA)" <ji...@apache.org>]

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

Bikas Saha commented on TEZ-1664:
---------------------------------

Should this be optional so that latency is not affected in the common case.
An extension of this would be for the client to be really thin. The existing thick client works as it does today. But the thin client basically looks at tez-site.xml, downloads the tar.gz locally (if needed by comparing checksums) and then starts using the local version.

> Add checks to ensure that the client and AM are compatible 
> -----------------------------------------------------------
>
>                 Key: TEZ-1664
>                 URL: https://issues.apache.org/jira/browse/TEZ-1664
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>
> There is a potential chance that a client is misconfigured wrongly to point to an incompatible tez tar ball on HDFS.
> Until we end up supporting either compatibility across various versions or uploading the tez tarball if not configured, we should do a version compatibility check and fail the AM if it was launched by an incompatible client. 



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