[jira] [Commented] (AMBARI-22386) Patch Upgrades Broken For Clients Due To Versioned LD Library

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-22386:
------------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Patch Upgrades Broken For Clients Due To Versioned LD Library
> -------------------------------------------------------------
>
>                 Key: AMBARI-22386
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22386
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.6.1
>
>         Attachments: AMBARI-22386.patch
>
>
> When services are patched to different versions, jobs being run in containers are unable to pickup the correct JARs from the {{LD_LIBRARY_PATH}} passed in via the job. 
> Consider the following situation:
> - Base cluster installed at 2.6.3.0-1
> - Enable some sort of codec, like snappy
> - YARN patched to 2.6.3.1-1
> - Hive patched to 2.6.3.2-1
> When Hive goes to run jobs on Tez or when jobs are run on MapR, whatever is sending the job is resolving the {{hdp.version}} to its own version. The box that the job runs on, however, might not have that specific versioned directory. 
> The problem can only be solved externally by providing a way to ensure that the native libraries are on every machine which could potentially run jobs. We could install bits on every host, but that would defeat the space-saving purposes of patch upgrades.
> Another solution is to ensure that the Tez and MapR tarballs have the required libraries and that those libraries are added to the classpath of launched jobs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)