[
https://issues.apache.org/jira/browse/FALCON-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088990#comment-15088990
]
Pallavi Rao commented on FALCON-1677:
-------------------------------------
My opinion on the approaches:
1) -1 for that. For one, it is backward incompatible. User won't expect a retry
on timeout. Secondly, there is no way to specify if user doesn't want to retry
on timeouts.
2) +1 for that. It is a viable option and simplest (for users and
implementation-wise) too.
3) 0 for that. Provides most flexibility to the user. But, not sure if so much
flexibility is required.
> 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)
