You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Narayan Periwal (JIRA)" <ji...@apache.org> on 2016/01/12 09:40:39 UTC
[jira] [Issue Comment Deleted] (FALCON-1677) Support re-tries for
timed-out instances
[ https://issues.apache.org/jira/browse/FALCON-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Narayan Periwal updated FALCON-1677:
------------------------------------
Comment: was deleted
(was: Addressed.)
> Support re-tries for timed-out instances
> ----------------------------------------
>
> Key: FALCON-1677
> URL: https://issues.apache.org/jira/browse/FALCON-1677
> Project: Falcon
> Issue Type: Bug
> Reporter: Pallavi Rao
> Assignee: Narayan Periwal
> Attachments: FALCON-1677-v0.patch, FALCON-1677-v1.patch, FALCON-1677-v2.patch
>
>
> Currently, Falcon retries only on failure. We should extend support in case of timed-out instances too. Earlier, since we were relying on post-processing to notify the instance status, this was not possible. Now that Falcon relies on Oozie JMS notifications, we can support retries for timed out instances too.
> If a dataset is expected to get delayed for a long time, the user is currently forced to supply a large timeout value. This is an overhead in terms of Oozie having to poll for that long. If we introduce retries, the timeout can be a reasonable value with periodic/exponential back-off retries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)