falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1677) Support re-tries for timed-out instances
Date Mon, 08 Aug 2016 09:39:20 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pallavi Rao updated FALCON-1677:
--------------------------------
    Fix Version/s: 0.9

> 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
>             Fix For: trunk, 0.9
>
>         Attachments: FALCON-1677-v0.patch, FALCON-1677-v1.patch, FALCON-1677-v2.patch,
FALCON-1677-v3.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)

Mime
View raw message