[
https://issues.apache.org/jira/browse/FALCON-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089079#comment-15089079
]
Ajay Yadava commented on FALCON-1677:
-------------------------------------
Option 2 looks good to me. To address the backward compatibility concerns, for
feeds you will need to introduce a new property in runtime.properties for retry
on timeouts and make it false by default. Although I feel that by default true
behavior is more useful, may be we should consider switching defaults in a
future version.
> 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
>
> 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)
