falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peeyush Bishnoi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-970) Replication not honouring availability flag other than _SUCCESS
Date Mon, 12 Jan 2015 08:22:34 GMT

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

Peeyush Bishnoi commented on FALCON-970:

[~pracheer] It looks like that this issue is similar to FALCON-237 . If yes, can you please
close this issue.

> Replication not honouring availability flag other than _SUCCESS
> ---------------------------------------------------------------
>                 Key: FALCON-970
>                 URL: https://issues.apache.org/jira/browse/FALCON-970
>             Project: Falcon
>          Issue Type: Bug
>          Components: replication
>            Reporter: Pracheer Agarwal
> I have specified a different availability flag(let's say feed.status) in my feed definition.
Replication instance correctly wait for that file before staring the replication, but it also
copies _SUCCESS flag at the target directory on completion.
> Also it is not guaranteed that replication process is copying feed.status flag at the
end of replication. 
> The problem comes with the consumer process in the target cluster. Sometimes it is starting
before the all the data is replicated. The reason is presence of feed.status file.

This message was sent by Atlassian JIRA

View raw message