You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:51:09 UTC
[jira] [Created] (OOZIE-217) GH-275: CreatedTime and NominalTime
uses different timezone
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OOZIE-217) GH-275: CreatedTime and NominalTime
uses different timezone
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-217.
----------------------------------
Resolution: Fixed
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-217) GH-275: CreatedTime and NominalTime
uses different timezone
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099897#comment-13099897 ]
Hadoop QA commented on OOZIE-217:
---------------------------------
LazyBoy248 remarked:
Duplicated
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira