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:19:09 UTC
[jira] [Commented] (OOZIE-343) GH-553: coord job should not
materialize new actions when WAITING actions exceed concurrency
[ https://issues.apache.org/jira/browse/OOZIE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100013#comment-13100013 ]
Hadoop QA commented on OOZIE-343:
---------------------------------
angelokh remarked:
Closed by b8a1f1cfed903fcfb015a9a0c0c23df7b09bd08f coord job should not materialize new actions when WAITING actions exceed concurrency.
> GH-553: coord job should not materialize new actions when WAITING actions exceed concurrency
> --------------------------------------------------------------------------------------------
>
> Key: OOZIE-343
> URL: https://issues.apache.org/jira/browse/OOZIE-343
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> for a 5min coord job in catch-up mode, it created actions for the 1st hour. so there were 1 action RUNNING, and 11
> actions WAITING. $concurrency=1. however it continued to create actions for the next hour, and the total number of
> actions was 24. with throttling implemented, the coord job should stop materialization for the 2nd hour.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira