falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Biswajit Nayak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-306) Feed late replication is not working
Date Sun, 06 Apr 2014 04:55:16 GMT

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

Biswajit Nayak commented on FALCON-306:

"late-arrival cut-off" is for to wait for the data to be present till that time. If the data
comes within that hour the replication should kick off.  Even if the directory is created
(unless until the availability flag is raised) it should kick off immediately. if the data
does not arrives within that hours the oozie action id goes to time-out state from waiting.

Have not used new falcon, so could not comment on that part if some logic has been changed.

> Feed late replication is not working
> ------------------------------------
>                 Key: FALCON-306
>                 URL: https://issues.apache.org/jira/browse/FALCON-306
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Raghav Kumar Gautam
>              Labels: falcon-regression
> *STR*
> - Source clusters have following folders:
>   at colo=ua3, partition=UK/${cluster.colo} folder=input-data/2014/02/05/22/08/UK/ua3
>   at colo=ua2, partition=US/${cluster.colo} folder=input-data/2014/02/05/22/08/US/ua2
> - Target cluster
>   at colo=ua1: folder=input-data/2014/02/05/22/08/
> - Upload some data in source folders
> - Replication goes through
> - Upload some more data in source folders
> - Late replication does not happen
> *Test*
> PrismFeedLateReplicationTest#multipleSourceOneTarget_pastData
> PrismFeedLateReplicationTest#multipleSourceOneTarget_futureData

This message was sent by Atlassian JIRA

View raw message