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:27:10 UTC

[jira] [Created] (OOZIE-96) GH-60: actions should not be materialized after nominal time for current mode jobs

GH-60: actions should not be materialized after nominal time for current mode jobs
----------------------------------------------------------------------------------

                 Key: OOZIE-96
                 URL: https://issues.apache.org/jira/browse/OOZIE-96
             Project: Oozie
          Issue Type: Bug
            Reporter: Hadoop QA


I ran a coordinator job under current mode, then check its status:

[chaow@pressglass examples]$ oozie job -info 0000007-100727102157647-oozie-chao-C

ID                            Created                Nominal Time
...
0000007-......@2  2010-07-27 19:41     2010-07-27 19:40
...

We see that creation time is after nominal time, which is not correct.
Note here the cluster is not stressed at all - so actions should be created a bit earlier than the nominal time.

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

        

[jira] [Commented] (OOZIE-96) GH-60: actions should not be materialized after nominal time for current mode jobs

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099794#comment-13099794 ] 

Hadoop QA commented on OOZIE-96:
--------------------------------

bansalmayank remarked:
Closed by 01bcec28b4cd0617206433c3cc9c004fd7f247b1 actions should not be materialized after nominal time for current mode jobs

> GH-60: actions should not be materialized after nominal time for current mode jobs
> ----------------------------------------------------------------------------------
>
>                 Key: OOZIE-96
>                 URL: https://issues.apache.org/jira/browse/OOZIE-96
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> I ran a coordinator job under current mode, then check its status:
> [chaow@pressglass examples]$ oozie job -info 0000007-100727102157647-oozie-chao-C
> ID                            Created                Nominal Time
> ...
> 0000007-......@2  2010-07-27 19:41     2010-07-27 19:40
> ...
> We see that creation time is after nominal time, which is not correct.
> Note here the cluster is not stressed at all - so actions should be created a bit earlier than the nominal time.

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

        

[jira] [Closed] (OOZIE-96) GH-60: actions should not be materialized after nominal time for current mode jobs

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik closed OOZIE-96.
---------------------------------

    Resolution: Fixed

> GH-60: actions should not be materialized after nominal time for current mode jobs
> ----------------------------------------------------------------------------------
>
>                 Key: OOZIE-96
>                 URL: https://issues.apache.org/jira/browse/OOZIE-96
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> I ran a coordinator job under current mode, then check its status:
> [chaow@pressglass examples]$ oozie job -info 0000007-100727102157647-oozie-chao-C
> ID                            Created                Nominal Time
> ...
> 0000007-......@2  2010-07-27 19:41     2010-07-27 19:40
> ...
> We see that creation time is after nominal time, which is not correct.
> Note here the cluster is not stressed at all - so actions should be created a bit earlier than the nominal time.

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