Workflow logical start time is not correct

Description

If I set a workflow to run every 5 minutes, the logical start time I get is not on the 5 minute mark.

This seems to be because the quartz job context does not return a correct time. If I set a breakpoint in DefaultSchedulerService, I can see incorrect times coming from context.getScheduledFireTime().

Release Notes

None

Activity

Show:

Terence Yim January 30, 2015 at 9:50 PM

The root cause is in CDAP-1322. Resolving this one as duplicate.

Sagar Kapare January 30, 2015 at 8:27 PM

context.getScheduledFireTime() is returning the correct time, however for some reason in distributed mode program options are not getting passed to the WorkflowDriver. In standalone mode however the program options get passed correctly. Digging further.

Duplicate
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Priority

Created January 30, 2015 at 6:43 AM
Updated December 9, 2020 at 8:58 PM
Resolved January 30, 2015 at 9:50 PM