You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/25 06:44:20 UTC

[jira] [Commented] (FALCON-298) Feed update with replication delay creates holes

    [ https://issues.apache.org/jira/browse/FALCON-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391423#comment-15391423 ] 

ASF GitHub Bot commented on FALCON-298:
---------------------------------------

GitHub user sandeepSamudrala opened a pull request:

    https://github.com/apache/falcon/pull/239

    FALCON-298. Feed update with replication delay creates holes

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sandeepSamudrala/falcon master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/239.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #239
    
----
commit 9e68a578328e284dcdf845ce32a0c48ac8dba36c
Author: sandeep <sa...@gmail.com>
Date:   2016-07-25T06:36:59Z

    FALCON-298. Feed update with replication delay creates holes

----


> Feed update with replication delay creates holes
> ------------------------------------------------
>
>                 Key: FALCON-298
>                 URL: https://issues.apache.org/jira/browse/FALCON-298
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: sandeep samudrala
>             Fix For: 0.8
>
>         Attachments: FALCON-298-v1.patch, FALCON-298-v2.patch, FALCON-298-v3.patch, FALCON-298.patch
>
>
> When feed is updated, falcon sets endtime of old coordinator to now and creates new coord with start time as now. But for replication update with delay, old coord's endtime is set to now and new coord's start time is set to now+delay. This creates a hole in scheduler



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)