[
https://issues.apache.org/jira/browse/OOZIE-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368334#comment-15368334
]
Rohini Palaniswamy commented on OOZIE-1402:
-------------------------------------------
You are changing the logic which is not right. You need to queue only if status
== false and that should be retained. What you need is
long addtionalDelay = isChangeInDependency ? 0: ConfigurationService
.getInt(CONF_COORD_INPUT_CHECK_REQUEUE_INTERVAL_ADDITIONAL_DELAY) * 1000L;
status == false means some inputs are still missing.
isChangeInDependency means we found some inputs. It could mean that we found
all inputs or some inputs are still missing
> Increase retry interval for non-progressing coordinator action with fix value
> -----------------------------------------------------------------------------
>
> Key: OOZIE-1402
> URL: https://issues.apache.org/jira/browse/OOZIE-1402
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Satish Subhashrao Saley
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1402-1.patch, OOZIE-1402-2.patch,
> OOZIE-1402-3.patch, OOZIE-1402-amend-1.patch
>
>
> Currently every coordinator action is retried to check data directory in the
> next minute.
> We could make it better by waiting longer for coordinator action that is not
> progressing (i.e. find no new directory) for repeated retries
> The waiting time should start from 1 minute for X retries. Then the action
> should wait for 2 minutes. After X retries it should wait for 3. The same way
> it will go to some max-wait-time and stay there until timeout
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
