You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2016/01/08 10:15:40 UTC
[jira] [Comment Edited] (FALCON-1737) Ensure
DataAvailabilityService handles timeouts across Falcon restarts
[ https://issues.apache.org/jira/browse/FALCON-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088941#comment-15088941 ]
Pallavi Rao edited comment on FALCON-1737 at 1/8/16 9:15 AM:
-------------------------------------------------------------
This JIRA is a result of review comments for FALCON-1230. Basically, the instance time_out is calculated from the time a new DataNotificationRequest is placed. When Falcon restarts, a refresh request will be placed. If the service has waited for 1 hr for a 2 hr time_out, after Falcon restart, it will end up waiting for 2 hrs all over again (instead of remaining 1 hr).
was (Author: pallavi.rao):
This JIRA is a result of review comments for FALCON-1230. Basically, the instance time_out is calculated from the time a new DataNotificationRequest is placed. When Falcon restarts, a refresh will be placed. If the we have waited for 1 hr for a 2 hr time_out, after Falcon restart, we will end up waiting for 2 hrs (instead of remaining 1 hr).
> Ensure DataAvailabilityService handles timeouts across Falcon restarts
> ----------------------------------------------------------------------
>
> Key: FALCON-1737
> URL: https://issues.apache.org/jira/browse/FALCON-1737
> Project: Falcon
> Issue Type: Improvement
> Components: scheduler
> Reporter: Pallavi Rao
>
> Follow up from review of FALCON-1230.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)