You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2016/01/20 23:39:40 UTC

[jira] [Resolved] (AMBARI-14678) RU - Oozie HA, Service Check fails since the pre-upgrade directive has multiple tasks that should run only on the specified hosts

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

Alejandro Fernandez resolved AMBARI-14678.
------------------------------------------
    Resolution: Fixed

Looks the the original patch didn't apply cleanly. Applied it again on branch-2.2,
commit 77cdf1b58308025e491116c70f26056c73977942

> RU - Oozie HA, Service Check fails since the pre-upgrade directive has multiple tasks that should run only on the specified hosts
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14678
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14678
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14678.trunk.patch
>
>
> STR:
> HDP 2.2
> Multiple Oozie Servers
> RU to HDP 2.3
> The pre-upgrade directive for Oozie has 
> {code}
> <pre-upgrade>
>   <task xsi:type="execute" hosts="all" summary="Shut down all Oozie servers">
>     <script>scripts/oozie_server.py</script>
>     <function>stop</function>
>   </task>
>   <task xsi:type="execute" hosts="any" summary="Upgrading the database and creating a new sharelib">
>     <script>scripts/oozie_server_upgrade.py</script>
>     <function>upgrade_oozie_database_and_sharelib</function>
>   </task>
> </pre-upgrade>
> {code}
> Notice that the first task runs on all hosts, and the second task runs on exactly one random host. The problem is that the scheduler runs both tasks in one stage on the union of these hosts. Therefore, the 2nd task runs on the wrong set of hosts.



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