[
https://issues.apache.org/jira/browse/OOZIE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated OOZIE-217:
-------------------------------------
Fix Version/s: pre-Apache
> GH-275: CreatedTime and NominalTime uses different timezone
> -----------------------------------------------------------
>
> Key: OOZIE-217
> URL: https://issues.apache.org/jira/browse/OOZIE-217
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
> Fix For: pre-Apache
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
