Return-Path: 
 <dev-return-1012-apmail-falcon-dev-archive=falcon.apache.org@falcon.incubator.apache.org>
X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org
Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id AECFD106F8
	for <apmail-falcon-dev-archive@minotaur.apache.org>;
 Wed, 18 Sep 2013 06:15:31 +0000 (UTC)
Received: (qmail 49401 invoked by uid 500); 18 Sep 2013 06:15:29 -0000
Delivered-To: apmail-falcon-dev-archive@falcon.apache.org
Received: (qmail 49341 invoked by uid 500); 18 Sep 2013 06:15:26 -0000
Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@falcon.incubator.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@falcon.incubator.apache.org>
List-Post: <mailto:dev@falcon.incubator.apache.org>
List-Id: <dev.falcon.incubator.apache.org>
Reply-To: dev@falcon.incubator.apache.org
Delivered-To: mailing list dev@falcon.incubator.apache.org
Received: (qmail 49333 invoked by uid 99); 18 Sep 2013 06:15:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Sep 2013 06:15:25 +0000
X-ASF-Spam-Status: No, hits=-2000.6 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with SMTP; Wed, 18 Sep 2013 06:15:20 +0000
Received: (qmail 47945 invoked by uid 99); 18 Sep 2013 06:14:55 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Sep 2013 06:14:55 +0000
Date: Wed, 18 Sep 2013 06:14:55 +0000 (UTC)
From: "Shwetha G S (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12658466.1374134785323.152808.1379484895411@arcas>
In-Reply-To: <JIRA.12658466.1374134785323@arcas>
References: <JIRA.12658466.1374134785323@arcas>
Subject: [jira] [Updated] (FALCON-50) Falcon replication having issue to s3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Shwetha G S updated FALCON-50:
------------------------------

    Description: 
Overview :- Replication of data from one cluster to s3 is not working.

Detail:-
Replication feed was submitted and scheduled through falcon. While only the retention bundle and co-ordinator (in oozie) are kicked up, could not see any sign of replication bundle or co-ordinator in oozie logs. Dont see any error in logs.

Below is the feed definition :-
{noformat}
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<feed name="process-name" description="process-name" xmlns="uri:falcon:feed:0.1">
    <frequency>hours(1)</frequency>
    <late-arrival cut-off="hours(6)" />
    <clusters>
        <cluster name="cluster1" type="source">
            <validity start="2013-07-17T00:00Z" end="2034-12-20T08:00Z"/>
            <retention limit="days(24)" action="delete"/>
        </cluster>
        <cluster name="cluster2" type="target">
            <validity start="2013-07-17T00:00Z" end="2034-12-20T08:00Z"/>
            <retention limit="days(90)" action="delete"/>
            <locations>
                <location type="data" path="s3://<bucket-name>/<path-folder>/${YEAR}-${MONTH}-${DAY}-${HOUR}/"/>
            </locations>
        </cluster>
    </clusters>
    <locations>
        <location type="data" path="/path/to/copy/${YEAR}/${MONTH}/${DAY}/${HOUR}/"/>
    </locations>
    <ACL owner="user" group="group" permission="0x755"/>
    <schema location="/schema/s1" provider="protobuf"/>
    <properties>
        <property name="queueName" value="queueName"/>
        <property name="jobPriority" value="NORMAL"/>
    </properties>
</feed>
{noformat}


  was:
Overview :- Replication of data from one cluster to s3 is not working.

Detail:-
Replication feed was submitted and scheduled through falcon. While only the retention bundle and co-ordinator (in oozie) are kicked up, could not see any sign of replication bundle or co-ordinator in oozie logs. Dont see any error in logs.

Below is the feed definition :-

?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<feed name="process-name" description="process-name" xmlns="uri:falcon:feed:0.1">
    <frequency>hours(1)</frequency>
    <late-arrival cut-off="hours(6)" />
    <clusters>
        <cluster name="cluster1" type="source">
            <validity start="2013-07-17T00:00Z" end="2034-12-20T08:00Z"/>
            <retention limit="days(24)" action="delete"/>
        </cluster>
        <cluster name="cluster2" type="target">
            <validity start="2013-07-17T00:00Z" end="2034-12-20T08:00Z"/>
            <retention limit="days(90)" action="delete"/>
            <locations>
                <location type="data" path="s3://<bucket-name>/<path-folder>/${YEAR}-${MONTH}-${DAY}-${HOUR}/"/>
            </locations>
        </cluster>
    </clusters>
    <locations>
        <location type="data" path="/path/to/copy/${YEAR}/${MONTH}/${DAY}/${HOUR}/"/>
    </locations>
    <ACL owner="user" group="group" permission="0x755"/>
    <schema location="/schema/s1" provider="protobuf"/>
    <properties>
        <property name="queueName" value="queueName"/>
        <property name="jobPriority" value="NORMAL"/>
    </properties>
</feed>
 

    
> Falcon replication having issue to s3
> -------------------------------------
>
>                 Key: FALCON-50
>                 URL: https://issues.apache.org/jira/browse/FALCON-50
>             Project: Falcon
>          Issue Type: Bug
>          Components: general
>            Reporter: Biswajit Nayak
>              Labels: operability
>
> Overview :- Replication of data from one cluster to s3 is not working.
> Detail:-
> Replication feed was submitted and scheduled through falcon. While only the retention bundle and co-ordinator (in oozie) are kicked up, could not see any sign of replication bundle or co-ordinator in oozie logs. Dont see any error in logs.
> Below is the feed definition :-
> {noformat}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <feed name="process-name" description="process-name" xmlns="uri:falcon:feed:0.1">
>     <frequency>hours(1)</frequency>
>     <late-arrival cut-off="hours(6)" />
>     <clusters>
>         <cluster name="cluster1" type="source">
>             <validity start="2013-07-17T00:00Z" end="2034-12-20T08:00Z"/>
>             <retention limit="days(24)" action="delete"/>
>         </cluster>
>         <cluster name="cluster2" type="target">
>             <validity start="2013-07-17T00:00Z" end="2034-12-20T08:00Z"/>
>             <retention limit="days(90)" action="delete"/>
>             <locations>
>                 <location type="data" path="s3://<bucket-name>/<path-folder>/${YEAR}-${MONTH}-${DAY}-${HOUR}/"/>
>             </locations>
>         </cluster>
>     </clusters>
>     <locations>
>         <location type="data" path="/path/to/copy/${YEAR}/${MONTH}/${DAY}/${HOUR}/"/>
>     </locations>
>     <ACL owner="user" group="group" permission="0x755"/>
>     <schema location="/schema/s1" provider="protobuf"/>
>     <properties>
>         <property name="queueName" value="queueName"/>
>         <property name="jobPriority" value="NORMAL"/>
>     </properties>
> </feed>
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira