falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1844) Falcon feed replication leaves behind old files when a feed instance is re-run
Date Thu, 03 Mar 2016 07:24:18 GMT

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

Pallavi Rao commented on FALCON-1844:
-------------------------------------

Marking this as backward incompatible as there is a slight change in behavior during replication
re-run.

> 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
>
> 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)

Mime
View raw message