[jira] [Resolved] (OOZIE-207) GH-256: CreatedTime and NominalTime uses different timezone

["Hadoop QA (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadoop QA resolved OOZIE-207.
-----------------------------

    Resolution: Fixed

> GH-256: CreatedTime and NominalTime uses different timezone
> -----------------------------------------------------------
>
>                 Key: OOZIE-207
>                 URL: https://issues.apache.org/jira/browse/OOZIE-207
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Hi,
> In the coordinator code, it compares the field nominalTime and createdTime to determine if a scheduled WF should time out or not.  
> 108                     long waitingTime = (actualTime.getTime() - coordAction.g    etNominalTime().getTime()) / (60 * 1000);
> 109                     int timeOut = coordAction.getTimeOut();
> 110  
> 111                     if ((timeOut >= 0) && (waitingTime > timeOut)) {
> in file command/coord/CoordActionInputCheckCommand.java
> I ran into an issue where a future job timed out so I investigate further into the code.  What I realize was my nominalTime was UTC (specify by the WF configuration) but the createdTime was in EST which was the timezone in my JVM.
> The createdTime was set in the following code..
> 821         coordJob.setCreatedTime(new Date()); // TODO: Do we need that? 
> in file command/coord/CoordSubmitCommand.java
> I believe this is a bug, we need to create the Date object using the timezone specified in the WF configuration.
> Please let me know what you guys think,  Thanks in advance.
> John

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira