[
https://issues.apache.org/jira/browse/HELIX-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579577#comment-14579577
]
Lei Xia edited comment on HELIX-600 at 6/9/15 11:23 PM:
--------------------------------------------------------
To be more specific, this only happens when you delete an existing queue, and
recreate it.
- stop the queue
- delete the queue (using taskDriver.delete(queueName) API )
- create a queue with new startTime recurrence parameter
If new startTime is a value in the future (say current-time + 5 minutes), Helix
is not scheduling the jobs event after startTime timestamp elapses.
was (Author: andrewlxia):
To me more specific, this only happens when you delete an existing queue, and
recreate it.
- stop the queue
- delete the queue (using taskDriver.delete(queueName) API )
- create a queue with new startTime recurrence parameter
If new startTime is a value in the future (say current-time + 5 minutes), Helix
is not scheduling the jobs event after startTime timestamp elapses.
> Task scheduler fails to schedule a recurring workflow if the startTime is set
> to a future timestamp
> ---------------------------------------------------------------------------------------------------
>
> Key: HELIX-600
> URL: https://issues.apache.org/jira/browse/HELIX-600
> Project: Apache Helix
> Issue Type: Bug
> Affects Versions: 0.6.3, 0.6.4
> Reporter: Karthiek
> Assignee: Lei Xia
>
> If we define a recurrent job queue with start-time value in the future (say
> current time + 5 minutes), Helix does not schedule the queue event after
> start-time timestamp elapses. Helix should schedule jobs once the recurrence
> timestamp is hit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
