[
https://issues.apache.org/jira/browse/OOZIE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052016#comment-14052016
]
Hadoop QA commented on OOZIE-1916:
----------------------------------
Testing JIRA OOZIE-1916
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1503
. Tests failed: 3
. Tests errors: 2
. The patch failed the following testcases:
.
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)
.
testActionInputCheckLatestActionCreationTime(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
.
testBundleEngineResume(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/1346/
> 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
> Assignee: Robert Kanter
> Priority: Minor
> Attachments: OOZIE-1916.patch
>
>
> 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".
> Make sure errors and edge cases are handled properly, including what happens
> when the leader dies without unregistering, etc.
> http://curator.apache.org/curator-recipes/leader-latch.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
