[
https://issues.apache.org/jira/browse/FALCON-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136494#comment-15136494
]
ASF GitHub Bot commented on FALCON-383:
---------------------------------------
GitHub user try0and1Again opened a pull request:
https://github.com/apache/falcon/pull/32
FALCON-383 Minimum value for oozie throttle
Please review then commit (RTC), or request clarification or changes.
Thanks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/try0and1Again/falcon FALCON-383
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/falcon/pull/32.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #32
----
commit 1bc4e4f147a68e781d46476a893634358d0807e8
Author: Mark Greene <[email protected]>
Date: 2016-02-07T22:32:50Z
FALCON-383 Minimum value for oozie throttle
----
> Minimum value for oozie throtle
> -------------------------------
>
> Key: FALCON-383
> URL: https://issues.apache.org/jira/browse/FALCON-383
> Project: Falcon
> Issue Type: Bug
> Reporter: Shwetha G S
> Labels: newbie
>
> Currently, throttle for oozie coord is set as 2*timeout/frequency. If the
> timeout is 20 hrs and frequency is 24 hrs, throttle will be set as 1 which is
> bad. Coord action re-run of a timedout instance puts the action in WAITING
> status and this blocks further materialisation in oozie. We should set
> default value to some sane value like 12 (which is the default value in oozie)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
