You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/03/26 00:17:15 UTC
[jira] [Updated] (FALCON-378) Feed status fails with NPE post
update when the new coordinator is in PREP state
[ https://issues.apache.org/jira/browse/FALCON-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Venkatesh Seetharam updated FALCON-378:
---------------------------------------
Attachment: test-update-feed.xml
test-update-feed-1.xml
oozie-coords.tiff
oozie-coord-new.tiff
test-update-feed-2.xml
> Feed status fails with NPE post update when the new coordinator is in PREP state
> --------------------------------------------------------------------------------
>
> Key: FALCON-378
> URL: https://issues.apache.org/jira/browse/FALCON-378
> Project: Falcon
> Issue Type: Bug
> Components: oozie
> Affects Versions: 0.4
> Reporter: Venkatesh Seetharam
> Attachments: oozie-coord-new.tiff, oozie-coords.tiff, test-update-feed-1.xml, test-update-feed-2.xml, test-update-feed.xml
>
>
> An NPE is thrown for status calls post feed update briefly between the new coord creation transitioning from PREP to RUNNING at:
> {code}
> org.apache.falcon.workflow.engine.OozieWorkflowEngine#getCoordActions
> Date iterEnd = (coord.getNextMaterializedTime().before(end) ? coord.getNextMaterializedTime() : end);
> {code}
> coord.getNextMaterializedTime() is null since the coord is in PREP state as the new coord's effective time is set as now() + 3 min. In reality, this is greater than 3 mins is my observation.
> {code}
> Feed updated at:
> Current time = Tue, 25 Mar 2014 21:54:00 GMT
> Old Coord:
> Start time = Tue, 25 Mar 2014 00:00:00 GMT
> End time = Tue, 25 Mar 2014 22:00:00 GMT
> Status = RUNNING
> New Coord:
> Start time = Tue, 25 Mar 2014 22:00:00 GMT
> End time = Wed, 26 Mar 2014 00:00:00 GMT
> Status = PREP
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)