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

Robert Kanter updated OOZIE-1916:
---------------------------------

    Description: 
We currently have a few tasks (e.g. Purging old jobs) that we only want to do 
in one Oozie server.  We currently simply check which Oozie server is first in 
ZooKeeper's list of servers (i.e. the order they connected).  We haven't seen 
any problems with this, but it might be a good idea to replace this with 
Curator's leader-latch, which sounds more robust.  

The leader path should probably be something like "/services/leader"

http://curator.apache.org/curator-recipes/leader-latch.html

  was:
We currently have a few tasks (e.g. Purging old jobs) that we only want to do 
in one Oozie server.  We currently simply check which Oozie server is first in 
ZooKeeper's list of servers (i.e. the order they connected).  We haven't seen 
any problems with this, but it might be a good idea to replace this with 
Curator's leader-latch, which sounds more robust.  

The leader path should probable be something like "/services/leader"

Once this is done, we also no longer need the internal leader-latch used by the 
ChildReaper in OOZIE-1906.


http://curator.apache.org/curator-recipes/leader-latch.html


> Use Curator leader latch instead of checking the order of Oozie servers
> -----------------------------------------------------------------------
>
>                 Key: OOZIE-1916
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1916
>             Project: Oozie
>          Issue Type: Improvement
>          Components: HA
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Priority: Minor
>
> We currently have a few tasks (e.g. Purging old jobs) that we only want to do 
> in one Oozie server.  We currently simply check which Oozie server is first 
> in ZooKeeper's list of servers (i.e. the order they connected).  We haven't 
> seen any problems with this, but it might be a good idea to replace this with 
> Curator's leader-latch, which sounds more robust.  
> The leader path should probably be something like "/services/leader"
> http://curator.apache.org/curator-recipes/leader-latch.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to