ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10436) RU - Fails if in Oozie if hadoop-lzo codec is enabled after version bits have been distributed
Date Fri, 10 Apr 2015 15:46:12 GMT

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

Hudson commented on AMBARI-10436:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2255 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2255/])
AMBARI-10436 RU - Fails if in Oozie if hadoop-lzo codec is enabled after version bits have
been distributed. (atkach) (atkach: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fc8552e54cf59b342de5f0ebbdfd26090780fd6b)
* ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs
* ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* ambari-web/app/messages.js
* ambari-web/app/styles/stack_versions.less


> 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)

Mime
View raw message