You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Jason Phelps (JIRA)" <ji...@apache.org> on 2018/05/03 11:30:00 UTC
[jira] [Comment Edited] (OOZIE-3214) Allow configurable timezone
for coordinators
[ https://issues.apache.org/jira/browse/OOZIE-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462299#comment-16462299 ]
Jason Phelps edited comment on OOZIE-3214 at 5/3/18 11:29 AM:
--------------------------------------------------------------
[~orova]/[~kmarton], for consistency's sake, I believe that it should follow the same behavior that the cron daemon does. See the [manpage for crond |[https://linux.die.net/man/8/crond]]
{quote}If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time has moved backward, care is taken to avoid running jobs twice.
{quote}
This means that in the winter to summer example, all of the jobs configured during the skipped hour of 2:00 AM to 3:00 AM should run immediately at 3:00 AM.
In the summer to winter example, I think there is already [some error checks|https://github.com/apache/oozie/blob/35451d50529634c9ce8730abe782bd4cf182b9a1/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L318] that will stop the first instance of the job from running, so it may be easier to keep as-is and have only the second execution to run, it will just need to be documented
was (Author: jphelps):
[~orova], for consistency's sake, I believe that it should follow the same behavior that the cron daemon does. See the [manpage for crond |[https://linux.die.net/man/8/crond]]
{quote}If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time has moved backward, care is taken to avoid running jobs twice.
{quote}
This means that in the winter to summer example, all of the jobs configured during the skipped hour of 2:00 AM to 3:00 AM should run immediately at 3:00 AM.
In the summer to winter example, I think there is already [some error checks|https://github.com/apache/oozie/blob/35451d50529634c9ce8730abe782bd4cf182b9a1/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L318] that will stop the first instance of the job from running, so it may be easier to keep as-is and have only the second execution to run, it will just need to be documented
> Allow configurable timezone for coordinators
> --------------------------------------------
>
> Key: OOZIE-3214
> URL: https://issues.apache.org/jira/browse/OOZIE-3214
> Project: Oozie
> Issue Type: New Feature
> Components: coordinator
> Affects Versions: trunk
> Reporter: Julia Kinga Marton
> Assignee: Julia Kinga Marton
> Priority: Major
>
> Right now in case of coordinators only daylight saving time corrections are applied, the processing timezone for the coordinators is always the Oozie processing timezone.
> It would be more transparent to have an option for changing the {{timezone}} attribute itself, such as an additional attribute in the {{coordinator.xml}} (meaning a new version of {{coordinator.xsd}}). I would make this option switched off by default(to have the actual behavior).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)