[jira] [Updated] (AMBARI-10436) RU - Fails if in Oozie if hadoop-lzo codec is enabled after version bits have been distributed

["Andrii Tkach (JIRA)" <ji...@apache.org>]

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

Andrii Tkach updated AMBARI-10436:
----------------------------------
    Attachment: AMBARI-10436.patch

> RU - Fails if in Oozie if hadoop-lzo codec is enabled after version bits have been distributed
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10436
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10436
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10436.patch
>
>
> There's a corner-case that can cause RU to fail if a user registers a version and installs it (i.e., distributes the bits to all of the hosts. Note that at this point there was no need to download hadoop-lzo jar), and then enables lzo compression, and begins the RU, then Oozie Server restart will fail because the lzo jar was never downloaded.
> lzo is enabled as follows.
> There are several ways to fix this corner case:
> 1. Force redistribution of bits for a version that is already INSTALLED. This is more general, and can help in other scenarios, so I think it's preferable. 
> 2. Detect what changes to the configs should transition INSTALLED versions as OUT_OF_SYNC; this is difficult to maintain.
> 3. Have Oozie Server RU Restart download the package; this is not desirable because the RU now has to do more work that could have been done up-front.



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