[
https://issues.apache.org/jira/browse/OOZIE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207754#comment-14207754
]
Hadoop QA commented on OOZIE-2063:
----------------------------------
Testing JIRA OOZIE-2063
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 1 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: 1555
. Tests failed: 4
. Tests errors: 0
. The patch failed the following testcases:
.
testActionKillCommandActionNumbers(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.
testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.
testMemoryUsageAndSpeed(org.apache.oozie.service.TestPartitionDependencyManagerService)
.
testRequeueOnException(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand)
{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/2090/
> Cron syntax creates duplicate actions
> -------------------------------------
>
> Key: OOZIE-2063
> URL: https://issues.apache.org/jira/browse/OOZIE-2063
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: trunk, 4.0.0, 4.1.0, 4.0.1
> Reporter: Robert Kanter
> Assignee: Bowen Zhang
> Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: cron.jpg, min.jpg, oozie-2063.patch
>
>
> If you use cron syntax, you'll get duplicate actions (i.e. actions with the
> same nominal time) at every throttle interval. For example, if throttle=12
> (the default), you'll have a duplicate action every 12 actions.
> Here's my coordinator:
> {code:xml}
> <coordinator-app name="cron-coord" frequency="*/5 * * * *" start="${start}"
> end="${end}" timezone="UTC"
> xmlns="uri:oozie:coordinator:0.2">
> <controls>
> <throttle>3</throttle>
> </controls>
> <action>
> <workflow>
> <app-path>${workflowAppUri}</app-path>
> <configuration>
> <property>
> <name>jobTracker</name>
> <value>${jobTracker}</value>
> </property>
> <property>
> <name>nameNode</name>
> <value>${nameNode}</value>
> </property>
> <property>
> <name>queueName</name>
> <value>${queueName}</value>
> </property>
> </configuration>
> </workflow>
> </action>
> </coordinator-app>
> {code}
> It runs every 5 min on the hour. I also ran a similar coordinator, but with
> the frequency set to {{coord:minutes(5)}}. I set the throttle to 3 so it
> would be easier to see the problem.
> Here are the two screenshots (make sure to either open them directly or widen
> the page to see the nominal time column):
> !cron.jpg!
> !min.jpg!
> As you can see in the cron screenshot, every 3 actions there's a duplicate
> action. And the next materialization time is the same as the latest
> materialized action, so it's going to do it again when it materializes more
> actions. On the minute screenshot, it's behaving correctly. You'll also see
> that the next materialized action is now 15 minutes ahead of the cron version!
> This has two major problems:
> - You have duplicate actions
> - The coordinator slowly gets further and further behind where it should be
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
