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/03/03 11:31:18 UTC

[jira] [Resolved] (FALCON-1844) Falcon feed replication leaves behind old files when a feed instance is re-run

     [ https://issues.apache.org/jira/browse/FALCON-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pallavi Rao resolved FALCON-1844.
---------------------------------
       Resolution: Fixed
    Fix Version/s: trunk

Issue resolved by pull request 60
[https://github.com/apache/falcon/pull/60]

> Falcon feed replication leaves behind old files when a feed instance is re-run
> ------------------------------------------------------------------------------
>
>                 Key: FALCON-1844
>                 URL: https://issues.apache.org/jira/browse/FALCON-1844
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>              Labels: backward-incompatible
>             Fix For: trunk
>
>
> When we re-replicate the data from one cluster to another, replication copies and overwrites old files, but, does not remove extra files in destination (that are not in the source dir any more). Example, first replication run copied 14 part files, on rerun, the source only had 13 part files, the 14th file still lingers in the destination.



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