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 07:27:11 UTC
[jira] [Created] (OOZIE-397) GH-647: rerun TIMEDOUT action and it
uses the timeout value and timedout again
GH-647: rerun TIMEDOUT action and it uses the timeout value and timedout again
------------------------------------------------------------------------------
Key: OOZIE-397
URL: https://issues.apache.org/jira/browse/OOZIE-397
Project: Oozie
Issue Type: Bug
Reporter: Hadoop QA
when rerun a TIMEDOUT action, since the clock time already passes the nominal time, it's like re-running this action in
"catch up" mode.
in "catch up" mode, the timeout value is set to "-1".
currently the rerun still uses the original timeout value as defined in coordinator.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-397) GH-647: rerun TIMEDOUT action and it
uses the timeout value and timedout again
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100067#comment-13100067 ]
Hadoop QA commented on OOZIE-397:
---------------------------------
angelokh remarked:
Closed by 33552eb72d10e0a9562710820f6233b5af6b9885 rerun TIMEDOUT action and it uses the timeout value and timedout again
> GH-647: rerun TIMEDOUT action and it uses the timeout value and timedout again
> ------------------------------------------------------------------------------
>
> Key: OOZIE-397
> URL: https://issues.apache.org/jira/browse/OOZIE-397
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> when rerun a TIMEDOUT action, since the clock time already passes the nominal time, it's like re-running this action in
> "catch up" mode.
> in "catch up" mode, the timeout value is set to "-1".
> currently the rerun still uses the original timeout value as defined in coordinator.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OOZIE-397) GH-647: rerun TIMEDOUT action and it
uses the timeout value and timedout again
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-397.
----------------------------------
Resolution: Fixed
> GH-647: rerun TIMEDOUT action and it uses the timeout value and timedout again
> ------------------------------------------------------------------------------
>
> Key: OOZIE-397
> URL: https://issues.apache.org/jira/browse/OOZIE-397
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> when rerun a TIMEDOUT action, since the clock time already passes the nominal time, it's like re-running this action in
> "catch up" mode.
> in "catch up" mode, the timeout value is set to "-1".
> currently the rerun still uses the original timeout value as defined in coordinator.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira