You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/09/17 03:49:54 UTC

[jira] [Updated] (OOZIE-1540) When oozie.zookeeper.oozie.id is not specified, its using a space instead of the hostname

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

Robert Kanter updated OOZIE-1540:
---------------------------------

    Attachment: OOZIE-1540.patch

The patch makes it so that whenever {{oozie.zookeeper.oozie.id}} is not set, is empty, or trim() results in empty string, it will use the hostname.  I also updated the docs and oozie-default.xml slightly.  

No tests because {{"oozie.http.hostname"}} isn't set during unit tests so I can't really check that its working.  I did verify that it works in a deployed set of Oozie servers.
                
> When oozie.zookeeper.oozie.id is not specified, its using a space instead of the hostname
> -----------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1540
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1540
>             Project: Oozie
>          Issue Type: Bug
>          Components: core
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Critical
>             Fix For: trunk
>
>         Attachments: OOZIE-1540.patch
>
>
> If you don't specify {{oozie.zookeeper.oozie.id}} it supposed to default to the hostname.  oozie-default.xml has this set to " " (space), which I misremembered how Configuration handled this, so currently, if you do this, all Oozie servers in the HA namespace will have the same id (i.e. " ") and will overwrite each other's entry in the service discovery in ZK, leaving only one.  This makes certain HA functionalities not work, including anything that relies on the service discovery such as log streaming.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira