You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Swapan Shridhar (JIRA)" <ji...@apache.org> on 2015/12/01 07:27:11 UTC

[jira] [Updated] (AMBARI-13824) Stop-and-Start Upgrade: Fix for Oozie Express upgrade issues from HDP 2.1 to 2.3

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

Swapan Shridhar updated AMBARI-13824:
-------------------------------------
    Attachment: Faclon-ozzie integration issue.png

'Faclon-oozie integration' issue screenshot.

> Stop-and-Start Upgrade: Fix for Oozie Express upgrade issues from HDP 2.1 to 2.3
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-13824
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13824
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0, 2.1.3
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>            Priority: Critical
>             Fix For: 2.2.0, 2.1.3
>
>         Attachments: AMBARI-13824.patch
>
>
> Problem : Unable to start Ozzie server while on upgrade from HDP 2.1 -> 2.3.
> Reason :  As 2.3 has symlinks instead of directory structure for "/etc/oozie/conf" and "usr/hdp/current/oozie-*/conf". 
> * -> "server" or "client"
> The symlinks are not properly set for Ozzie Server and client after the upgrade. 
> Resolution : Added a new class and comamnd "CONFIGURE_FUNCTION" to get the sym links working.
> After the upgrade, the symlinks are :
> ================================================
> /etc/oozie/conf -> /etc/oozie/2.3.4.0-3204/0
> /usr/hdp/current/oozie-server/conf -> /etc/oozie/2.3.4.0-3204/0
> ================================================
> P.S. The changes are generic in "conf_select" for setting the sym links. Thus, other services also should be having their symlinks working in 2.1->2.3 upgrade path.



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